Synthflow Client Workspace Setup (Onboarding)

Synthflow Client Workspace Setup (Onboarding)

1. 01

   Confirm the client clears Synthflow's enterprise floor before opening a workspace

   Enterprise contracts start at $30,000 annually, scoped around call volume, concurrency, telephony setup, integrations, security needs, and launch support. If the client cannot commit to that annual figure, stop here and route them to a lower-cost voice tool. This gate protects the agency from absorbing scoping work on deals that will never close.

2. 02

   Build the first call flow in the visual Flow Designer

   Map the client's inbound and outbound paths as separate branches: customer service, appointment booking, lead qualification, and receptionist routing. Connect APIs and business logic inside the designer rather than hardcoding them downstream, so the agency can revise flows without a redeploy.

3. 03

   Choose the telephony path: Synthflow Native Telephony, SIP trunking, or approved enterprise telephony

   The contract line item covers all three. Pick native telephony for greenfield clients, SIP trunking where the client already owns numbers, and approved enterprise telephony when the client runs Cisco or Genesys. Telephony choice drives the concurrency plan, so settle it before load testing.

4. 04

   Wire CRM, calendar, contact-center stack, webhook, API, and knowledge-source integrations

   Synthflow connects to HubSpot, Freshworks, Zapier, and 200-plus tools. For each connection, verify data sync in both directions: a booking written to the calendar must appear in the CRM, and a CRM status change must suppress further outbound attempts. Broken sync is the most common cause of duplicate client calls.

5. 05

   Configure concurrency, routing, escalation paths, handoffs, and fallback logic

   Set the concurrency ceiling to the client's contracted level, then define what happens at the ceiling: queue, overflow to a second agent, or fall back to a human queue. Write the human handoff triggers explicitly (frustration signals, repeated intent misses, VIP caller IDs) so the agent does not improvise escalation.

6. 06

   Run accuracy and compliance tests in the Test Center

   Test voicemail detection, contextual routing, SMS follow-up triggers, and escalation behavior before any live number points at the agent. Log the pass rate per flow branch. Do not deploy a branch that has not been tested against a real call recording from the client's existing phone system.

7. 07

   Complete the security and data-handling review with the client's stakeholders

   The enterprise contract includes MSA/DPA support, data handling review, workspace controls, and enterprise security review. Schedule this before go-live, not after, because healthcare, financial services, and legal clients will not sign a retainer until their compliance lead has seen the workspace controls.

8. 08

   Hand the workspace to the delivery pod with a monitoring cadence attached

   Assign named owners for call quality review, flow revision requests, and integration breakage. A Synthflow retainer only holds if someone is watching the call logs weekly; an unmonitored agent degrades quietly and the client attributes the drop to the agency, not the model.