White-label AI receptionist for agencies

Define one client’s reception workflow

Start with a written brief for the front desk. Record opening hours, services, service area, approved answers and what the agent must leave to a person. Decide whether a caller should receive information, request a callback or book through a connected calendar.

• Specify the greeting and any required AI or recording disclosure
• Name the staff contact and the situations that require escalation
• Agree on what happens after hours or when staff cannot answer

Choose a plan with room for client workspaces

Growth costs $149/month and includes white-label branding, 500 minutes, 10 agents, five total workspaces and 5 concurrent calls. The agency workspace uses one of those five slots, leaving up to four client workspaces if no others exist. These are organization limits, not a fresh allowance for each client. Enterprise starts at $499/month with 2,000 included minutes, 15 total workspaces and 5 concurrent calls.

• Free and Starter do not include white-label branding
• Browser tests consume minutes; budget for testing as well as live calls
• Check current pricing and carrier costs before quoting the client

Build and review the client’s Agent Spec

Create a client workspace and add that business’s approved knowledge and integrations. Generate the agent from the brief, then review the Agent Spec JSON: goals, conversation flow, allowed tools, guardrails and handoff behavior. Confirm that calendar and other connections belong to the intended client before publishing a version.

Apply branding within the supported limits

Configure workspace branding and check the hosted agent share page. Its hide-branding setting removes VoiceForge promotional links; it is not a promise that every platform surface is rebranded. A custom-domain field is available in settings, but custom-domain serving is not currently implemented. Share the hosted URL you have verified with the client.

Connect the number and prove staff handoff

Paid plans support phone setup, including client-owned Twilio numbers. Agree who controls the carrier account, who pays its charges and who can change routing. After browser tests, assign the intended agent and test an inbound call through the real number. Verify the configured transfer destination and agree on a callback fallback when a person is unavailable.

• Call during opening hours and after hours
• Request a person and test an unanswered transfer
• Confirm callback details are available to the staff member responsible

Run the client acceptance checklist

Write down expected outcomes and review the transcript and tool results for each test. Test on the phone route you will deploy; a Free browser test does not exercise a live phone number or carrier connection. Fix failures and repeat the affected scenarios before client sign-off.

• Ordinary question: use the approved business information
• Unknown answer: acknowledge the limit and offer the agreed next step
• Booking: confirm only after the connected calendar reports success
• Interruption or corrected details: retain the caller’s final request
• Failed integration or unavailable staff: explain the failure without claiming success

Hand over ownership and review live calls

Give the client the approved agent version, tested phone number, access appropriate to their role, a support contact and the agreed escalation process. Assign responsibility for updating hours and knowledge, reviewing transcripts and checking usage. Confirm consent, opt-out status, calling windows and required disclosures before any outbound follow-up; inbound reception does not authorize a callback campaign.

Questions, answered.