Knock Client Workflow Build and Handoff (Delivery)

Knock Client Workflow Build and Handoff (Delivery)

1. 01

   Confirm the client's Knock plan tier before scoping work

   Starter runs $250/month with 50K messages, 2.5K guide active users, and 2,000 AI agent credits. Map the client's expected monthly message volume and guide active users against those ceilings so the retainer does not absorb overage costs. Enterprise is quote-only and adds per-customer branding, custom roles, translation, SCIM, and SAML 2.0 SSO.

2. 02

   Configure channel inputs in the client workspace

   Set email configuration, SMS provider configuration, and brand styles with voice and tone. Knock setup complexity is medium and time-to-value is days, so run an internal validation send on each channel before committing to a client go-live date.

3. 03

   Draft the workflow as a natural language prompt to an AI agent

   Write the prompt for Claude, ChatGPT, Cursor, or Grok covering triggers, delays, branches, and agent steps. Knock assembles the workflow from that prompt, so the prompt must name the client's event triggers and the channel for each branch.

4. 04

   Review the generated workflow against the client's journey map

   Check every trigger, delay, and branch the agent produced. Confirm in-app guides (banners, modals, cards, tooltips) and one-time broadcasts are placed where the client expects them, and correct any branch the prompt misread.

5. 05

   Wire recipient data and event triggers to the client's app or CRM

   Import recipient data and connect the client's event source through the documented webhook setup. Test with a seeded recipient list before switching on live traffic.

6. 06

   Run a staged send across all five channels

   Send test messages through email, SMS, push, in-app, and chat to a small internal list. Verify personalized message fields render correctly and that transactional alerts fire on the right trigger.

7. 07

   Hand off with a monitoring routine in unified analytics

   Walk the client through the unified analytics view and agree a review cadence. Record which workflows the agency owns versus which the client edits, since Enterprise custom roles and permissions govern that split.