Before you connect WhatsApp
WhatsApp is often the highest-intent messaging channel for sales, support, bookings, and order follow-up. Before connecting it to Interlinked, make sure the business has the right Meta access, a clear workflow, and approved business context for the AI agent.
You should know which workflow the agent will support before going live: retail shipping, pickup, appointment scheduling, lead qualification, paid appointment booking, or handoff-focused service.
Requirements
- Access to the relevant Meta Business assets.
- Permission to connect the WhatsApp Business channel.
- A completed or drafted Interlinked onboarding setup.
- Business context, catalog or service details, and handoff expectations.
Setup path
1. Confirm the workflow
In Interlinked, choose the workflow that matches how the business should operate. WhatsApp behavior changes depending on whether the agent is collecting order details, qualifying leads, booking appointments, or routing conversations to a human.
2. Add business context
Complete the onboarding wizard with company details, agent identity, catalog or service information, locations, delivery or pickup rules, and any qualification questions the workflow requires.
3. Connect WhatsApp
Use the channel setup flow in the Interlinked workspace to connect WhatsApp. Follow the Meta authorization steps and complete any required checks before publishing the agent.
4. Publish and review
After publishing, monitor WhatsApp conversations in the CRM. Use manual control when a customer needs human judgment, payment review, or a response outside the approved business context.
Operational checks
- Test a product or service question.
- Test a handoff request.
- Test the workflow-specific path, such as booking or order collection.
- Confirm the team knows where to review CRM conversations.
- Confirm any retail orders or appointment activity appears in the expected workspace area.
What not to assume
Connecting WhatsApp does not automatically solve every integration need. Keep the AI grounded in approved Interlinked context, and route sensitive, account-specific, or operational exceptions to a human reviewer.