Multi-select plus one action panel — select across filters, then act on the whole set at once

1. Checkbox per row, select-all on the header, and select-all-matching for the whole filter — not just the visible page.
2. Selection persists across filter and search changes, so a set can be assembled in several passes.
3. One action panel on the selection: change status, message owners, resend T&Cs, enable billing, export.
4. Going Active runs the readiness check (B4) first and holds incomplete groups in Draft with the reason.
5. Selection survives the action, so operations chain on the same set.

Bulk-add group custom attributes and assign the OU across a selection — one operation instead of one visit per group

1. Select the groups, set their Organizational Unit once for the whole set.
2. Add group custom attributes in bulk — key and value written to every selected group.
3. Applies to the selection from A1, so the same set can be configured and activated in sequence.
4. Every write lands in the group change log, so a bad bulk edit can be traced and reversed.

Bulk billing configuration — payment method, pricing and commitments set across a selection in one operation

1. Payment method and terms chosen once: automatic card payment, or invoice with terms.
2. Pricing period selector — previous, current or next month — so a wave can be priced ahead of go-live.
3. Base fees, per-message rates, minimum spend and corporate credit set for the whole selection; blank fields are left untouched.
4. Address and payment pull from the signup record (A4) wherever one exists.
5. The Stripe write happens once per operation; failures return as a per-group list.

Capture the card during self-serve signup, before it can become a blocker

1. Card capture is a required step in the in-app signup form, before submit.
2. Owner-only permission is the thing in the way — see C6.
3. A group cannot reach Active without a card on file.

A team-scoped registration link, emailed to the location, so signup attaches to the right Team on arrival

1. The real fix is upstream: each location receives an email carrying a URL scoped to its parent Team.
2. Registering through that URL attaches the location to the correct Team — no guessing, no post-hoc reconciliation.
3. Only then is an arrival queue meaningful: signups land against a known Team, with an owner and an SLA.
4. Row shows the registry check result (C1) and hosting completeness (A8).

A bulk Message Owners action — pick a template, send now or schedule it to fire with the wave

1. One send addressed to the owner user on each selected group record — no more one-at-a-time password-reset emails.
2. Pick from named templates: go-live announcement, welcome, card-on-file, training invitation.
3. Send now, or schedule to a date and time so the invite fires with the wave instead of on import.
4. The panel states its own reach before you confirm — how many owners will receive it, and how many groups have no owner user at all.
5. Groups with no owner are surfaced as a count, not a silent failure.

In-product attribute editing, with bulk apply from the Group Operations page

1. Group custom attributes editable in-product by CSMs — no SFTP, no transformer.
2. Bulk apply across a selection from the Group Operations page.
3. Change log, so a bad bulk edit can be traced and reversed.

One intake form that branches on how the number is acquired, checks host-ability before asking anything else, and captures the signer’s authority

1. Screen one is a single question — keep your calls, move the number, or get a new one. Acquisition decides whether an LOA is needed at all.
2. The carrier check runs immediately on the number and gates the rest of the form: hostable, mobile, not hostable, or check failed.
3. Host and port collect the LOA set — legal name as it appears on the phone bill, structured service address including County, signer name, email and role.
4. A non-skippable confirmation that the signer is authorised on the account. A name alone is what got Primrose Rockland rejected at T-1 day.
5. Buy is three fields and no LOA. Nobody sees fields for a path they are not on.
6. Fields are carrier-agnostic, so nothing is thrown away at the Bandwidth migration.

Configuration Profile selector — pick one of four by name, and the settings follow

1. Four named profiles replace nine ad-hoc combinations of four settings.
2. Pick one at team creation; the underlying settings follow automatically.
3. Invalid combinations become unreachable; existing teams get audited once.

Search and buy in-product via the Cloudflare Registrar API

1. Search availability and buy the short domain from inside Voxie.
2. Part of the team creation checklist rather than tribal knowledge.
3. Ownership and expiry visible on the team record.

Let a document target a subset of Groups, and let more than one document be active at once — legacy acceptances stay frozen against what was actually signed

1. A Group sits in one of three states: no terms, a single document, or one specific active document out of several.
2. Creating a document asks who it applies to — all Groups, a cherry-picked list, or net-new Groups from the effective date.
3. Wave 1 stays on the document it signed, marked Legacy: kept for audit, not editable, never re-triggered.
4. The list view gains an Applies to column, and a Coverage view shows which Groups answer to which document.
5. Corporate-owned Groups stay exempt and short-circuit before any targeting is evaluated.

Kill switch plus export — and self-serve signup fixes the root cause

1. Admin override to unfreeze a location without waiting on acceptance.
2. Export of every group in Not Accepted, with the address it was sent to.
3. Root fix: signup guarantees a real human owner email exists (front door ①).

Define collections by group custom attribute instead of a hand-picked list — an attribute-defined collection has no ceiling

1. A collection defined by an attribute value rather than an enumerated list of groups.
2. Every group carrying the value belongs to it, so 450 or 600 groups join without anyone picking them 50 at a time.
3. Depends on bulk attribute writing (A2) — set the attribute once across the wave, the collection follows.
4. The cap itself stops mattering rather than needing to be raised.

Trigger Jean’s two templates on state change — both are already written

1. Welcome email fires when a signup is received; go-live email when status becomes Active.
2. Jean’s two templates, wired to the state change. No new copy needed.
3. Sent to the owner email captured at signup, with the CSM copied.

A readiness check that gates the bulk activate — nothing flips live until it passes

1. Change status runs the check before anything moves: groups that pass flip, groups that fail stay exactly as they were.
2. Failures are broken into named reasons — no owner user, T&Cs not accepted, no phone number, not in a verified campaign, billing incomplete — counted per operation.
3. Read from the columns already on the row, so it needs no new platform state; the same filters narrow the selection before you ever open the action.

The ops page retires them. One row per group, live, instead of six hand-maintained trackers

1. Every field the trackers hold already exists in Core, Twilio, Bandwidth or Stripe.
2. Surfacing existing data is exactly what Lucas can ship without Graham.
3. Tim: “you’ve gotten rid of a spreadsheet, because now that table is telling us all of the critical questions.”

Surface it at team creation, inside the configuration profile selector

1. The setting moves out of hidden team settings and onto the creation screen.
2. Shown inside the configuration profile selector (B3), with its consequence stated in plain words.
3. Import respects it explicitly instead of silently defaulting to Active.

Deferred. Active auto-enrolling into collections changes how the platform behaves — that is Graham, and Aug 10 ruled it out of the sprint

1. Seba’s Aug 5 proposal: a collection that only accepts Active groups enrols each new one automatically.
2. It is platform logic, not a UI — squarely on Graham’s side of the build line.
3. Aug 10: “we cannot allocate time the sprint after.” Onsite discussion topic, not a build.

The phone number is the duplicate key. The intake form looks it up in Voxie before the carrier check, so a duplicate is caught before the Group exists

1. Nobody is asked for an External ID — a franchisee does not know theirs. The number they are already typing is a better key than one they would have to look up.
2. Three signals are checked at once: the number itself, brand plus location name, and the service address on file.
3. Exact match on the number blocks submit and routes to the CSM who owns that Group, showing its External ID, owner and status.
4. Near match warns and offers the candidates — “use this Group” or “none of these” — rather than blocking.
5. Runs before the carrier check, so nobody fills in an authorisation for a location that already exists.

Required-field validation at team creation

1. The field becomes required at Team creation, with format validation.
2. Lookup against HubSpot so the ID is verified, not merely present.
3. Existing teams surface in a backfill list.

Seed the compliance automations as a step in New Team set-up, not a button someone has to remember

1. A Compliance step in the New Team flow seeds start/stop compliance automations on the team as it is created.
2. Idempotent, so re-running it is safe; it shows as an unchecked item until it has actually run.
3. Sits alongside Intelligent Inbox and the owner terms send, so all three one-time-per-brand chores happen in the same pass.

Submit to TCR directly from Kiosk, with the Messaging Registration skill running inline as pre-validation — registration is per brand and one-off, so it is not blocked by the Bandwidth timeline

1. Registration is per brand and happens once; assigning numbers is per group and happens at the aggregator. This surface ends where that begins.
2. Step 0 is the landing view: brand identity status, vetting, every campaign, and each carrier’s decision — nothing shows this today.
3. Three different things are called status — TCR campaign, per-carrier decision, and DCA sharing. They render as three fields, never one badge.
4. Use-case qualification reads from TCR per brand: which carriers qualify, actual tpm, and how many samples each requires — which then configures the campaign form.
5. The skill’s accumulated pass/fail rules run in-form before submit. That is the feature; it replaces the Twilio FastTrack safety net we are losing.
6. Rejection categories deep-link to the field that caused them, then fix → re-share → nudge — branched by aggregator, because Bandwidth does not support the TCR nudge.

Make AI enablement a default go-live step

1. Intelligent Inbox enabled as a default step at go-live.
2. Appears on the readiness check (B4) so it cannot be quietly skipped.
3. Adoption visible per brand.

Unblock Owner provisioning — the answer is needed before anything else is specced

1. Answer first: why is Owner blocked in user import?
2. If it is permissions hygiene, allow Owner on import and on self-serve creation.
3. If it is architectural, self-serve needs a payment path that isn’t Owner-gated.

Self-serve training signup in the same form. Delivery model goes to the CS session

1. The franchisee picks a training slot inside the signup form.
2. Slot capacity is visible, so wave size and training capacity become the same number.
3. Delivery model stays with CS — product only books it.