Quiverflow White-Label Sub-Account Provisioning (Onboarding)

Quiverflow White-Label Sub-Account Provisioning (Onboarding)

1. 01

   Create the client sub-account from the agency white-label dashboard

   Confirm the client's brand assets (logo, sending domain, reply-to address) are loaded before any contact import, because the sub-account inherits the agency's white-label shell and retrofitting branding after the first campaign forces a re-verification of the sending domain.

2. 02

   Set the contact ceiling and user licenses on the sub-account

   Quiverflow's flat plans include unlimited contacts and user licenses, so the constraint is not seat count but usage: decide up front who on the client side gets login access, since every additional user can trigger AI voice agents and SMS sends that bill per unit.

3. 03

   Wire the calendar layer before building any booking workflow

   Connect Google Calendar or Outlook Calendar at the sub-account level, then test a booking round-trip. Appointment sync failures surface later as missed-call follow-ups, which is the most expensive failure mode on a voice-agent retainer.

4. 04

   Map the two-way channels the client will actually staff

   Quiverflow supports Messenger, chat, email, phone, and SMS in one inbox. Turn off any channel the client has no human to answer, because an unanswered chat thread reads to the end customer as a broken business, not an unstaffed one.

5. 05

   Build the first automation workflow from a single trigger

   Start with one trigger (new lead captured on a landing page or form) and one sequence (SMS plus email follow-up). Quiverflow's workflow automation is where agency margin lives, so ship one working workflow before layering AI voice agents on top.

6. 06

   Configure the AI voice agent and set a per-call budget guardrail

   Voice calls bill at $0.26/minute and SMS at $0.0166/segment. Write the client's expected monthly call volume into the retainer scope and set an internal alert threshold, because a single misconfigured outbound campaign can consume the month's margin in days.

7. 07

   Publish the lead capture landing page and connect it to CRM intake

   Quiverflow builds landing pages and forms natively. Point the form at the pipeline stage you created in step five, then submit a live test entry and confirm it appears in the client's contact record with the correct source tag.

8. 08

   Hand off with a written channel and escalation map

   Deliver a one-page document listing which channels the agency monitors, which the client owns, response-time expectations, and the monthly usage report cadence. This is the artifact that keeps a white-label retainer from drifting into unpaid support.