V3.1 is the release where Nida stopped being a set of places to work and started deciding with you. Three things landed together: an Email Marketing module that writes its own sequences, Decision Models that rank what to do next from your live CRM data, and an Agency Command Center with a support desk that escalates into Nida. Underneath all of it, the platform started keeping receipts — every lead, booking, payment and automation logs itself.

Email Marketing: sequences, not blasts

Sending one email is easy. Sending the fifth email to the right person at the right time is a data problem, and most small businesses solve it by not solving it. The Email Marketing module in V3.1 ships the whole loop:

• Sequences. Build a multi-step flow — intro, value, proof, offer, follow-up — and enrol contacts into it. Each step has its own copy and wait time, and the module keeps the per-sequence list right next to the editor.
• AI writes the design and the sequence. Describe the offer and the audience, and Nida generates the sequence structure and the email design in one pass. You edit like an editor, not like a template wrangler.
• Delivery log. Every send is recorded with its delivery state, so "did they get it?" is a lookup instead of a guess.
• Unsubscribe, handled. The one-click opt-out is part of the module, not something you bolt on and hope.
• Replies land where you read. Sequences go out through the mailbox connected to the workspace, under your domain and your signature — not a shared relay that trashes deliverability.

For agencies this is the piece that usually forces a second subscription. Here it sits in the same workspace as the CRM that produced the list, which is why the targeting is real rather than aspirational.

Decision Models: a ranked answer to "what next"

Dashboards show you numbers. They rarely tell you what to do with them. The Decision Model in V3.1 produces a decision brief at the top of the dashboard: a ranked, repeatable answer built from your own CRM data — stalled deals, unanswered leads, jobs that should already be invoiced, contacts going cold.

Two properties matter:

• Ranked, not dumped. It orders work by what it costs you to ignore it, so the first line is the only line you have to read.
• Repeatable. Same inputs, same output. It is a model over your data, not a mood — you can argue with it, and you can act on it.

Most small-business software answers "what happened". A decision model answers "what now" — and it has to be able to explain itself, or nobody trusts it twice.

Agency Command Center, and a support desk that escalates

Nida's agency layer got a single command center: every client workspace, their health, and their open work in one view instead of a tab-and-hope routine. Support ticketing was unified in the same release — client tickets and Nida's own desk in one queue, so an escalation to our team rings the bell in Nida rather than getting copied into an inbox nobody owns. Team members get read the directory and the queue in one server-side call, and an invited teammate is now let in rather than locked out.

Everything logs itself

The quietest change in V3.1 is the one you will miss until it saves you: activity logging. Leads, bookings, payments and automations each write their own record as they happen. That is what makes the Decision Model and the Agency Command Center honest — they read a history that exists, instead of reconstructing one from hopes and timestamps.

What else tightened up

• Bookings, reminders and SMS were hardened against the real-world cases (duplicate reminders, stale statuses, attribution) that a QA pass caught before customers could.
• Voice and dashboard stopped reporting stale call statuses and started logging real call durations.
• Access now follows the plan consistently: agency modules unlock per plan, and every plan can still reach support.
• Forms never drop a captured answer again — every submission reaches both the lead and the contact record, even when the underlying table is missing a mapped column.

From a captured lead to a sequence, in four moves

The point of putting email in the same platform as the CRM is that the handoff disappears. A concrete pass through it:

1. A form fills in. The contact and the lead are created together, with every captured answer attached — not just the name and email, but the column that actually qualifies them.
2. The pipeline stage moves (or the automation does it for you), and the activity log records what happened and when.
3. The sequence enrols. Build it once from the offer and the audience; Nida writes the structure and the design, you edit the copy, and every send from then on is a step in a flow rather than a one-off blast.
4. The decision brief notices. If someone replies, books, or goes quiet long enough to matter, it surfaces in the ranked list at the top of the dashboard — which is the difference between "we sent an email" and "this is being worked".

None of that requires an export, a CSV, or a second login. That is the whole argument for a platform over a stack of tools.

Who V3.1 is for

Agencies get the shortest path to recurring revenue: client workspaces, an Agency Command Center that shows what needs attention across all of them, white-label branding, and an email module they no longer have to buy separately and stitch on.

Service businesses — contractors, clinics, salons, field teams — get the pieces that stop money leaking: leads that cannot be dropped silently, sequences that follow up without anyone remembering to, and a ranked list that says what to do first this morning.

FAQ

Do I need a separate email tool to use the sequences?

No. Connect the mailbox you already send from in workspace settings; the module sends through it, keeps the delivery log, and honours the one-click unsubscribe.

What does the Decision Model need to work?

Your workspace's own activity: deals, leads, bookings, payments and follow-ups. The more of your business runs in Nida, the sharper the ranking — this is one of the reasons we care so much about everything logging itself.

Can I resell Email Marketing to my own clients?

Yes. Module access follows the plan, and the whole platform is white-label — your domain, your branding, your portal. Your clients see your product, not ours.

Is V3.1 included in my plan?

Yes. V3.1 features ship to existing workspaces; plan gating applies to the agency and volume modules, exactly as before.

What comes next

V3.1 made Nida decide with you. V3.2 opens the doors outward — see the V3.2 release on the Integrations Hub, where your workspace connects to the tools you already pay for and to ChatGPT, Codex and Claude.

Want to see it on live data instead of screenshots? Pick a plan and open a workspace — the onboarding wizard builds your pipeline, business profile and branding in one pass.

← Back to the blog