Product documentation for teams operating Watzlink day to day.
This page is the practical starting point for setup, flow building, inbox work, campaigns, AI usage, and integrations. It is written for operators who need to launch safely and troubleshoot quickly.
Operator-first guidance
Focus on the workflows people actually run: connecting accounts, editing flows, handling inbox work, and shipping campaigns.
Built around the real stack
The docs reflect the live product shape: flows, inbox, campaigns, AI, CRM, queues, and connected services.
Safer launch path
Start small, test with a real number, then add complexity only after the base flow and operational path are stable.
The shortest path from first setup to repeatable operations.
Use the sections below in order if you are launching from scratch, or jump directly to the area you need to change inside the product.
Connect a number and launch your first working automation fast.
The shortest path is: connect WhatsApp, create a basic flow, publish it, and test from your own phone before adding conditions or integrations.
Build conversation logic visually without losing control of execution.
Flows are the operating core of Watzlink. Teams can design responses, branch on conditions, store answers, and hand off to humans without writing code.
Keep humans in the loop when a conversation should leave automation.
Automation should cover first response and routing, while the inbox stays available for exceptions, escalations, and high-value conversations.
Run queued outbound work with visibility into steps and enrollments.
Campaigns and broadcasts rely on the queue layer, so teams can plan structured outreach instead of firing one-off sends manually.
Mix automated replies with stored customer context instead of generic responses.
Watzlink already includes AI and CRM-oriented surfaces, so teams can combine contact context, saved notes, and operator guidance in one workspace.
Connect external systems only after the core operating flow is stable.
Integrations work best when the base workflow is already clear. Start with a working internal process, then connect APIs, Sheets, or other services.
Common questions teams hit while setting up and operating the system.
Use this section as the fast reference when you need to diagnose a broken path, empty variables, or uncertain launch behavior.
How do I build my first flow without overcomplicating it?
Start with one trigger, one message, and one question or branch. Test that path from your own WhatsApp account before adding AI, delays, or integrations.
Where do variables come from?
Variables are created by user answers, saved data steps, and integration responses. Once captured, they can be reused inside later messages and conditions with {{variableName}} syntax.
When should the team use the inbox instead of the flow builder?
Use flows for repeatable logic and the inbox for manual review, escalation, and relationship-sensitive conversations where a human should take over.
What is the safest way to test before going live?
Publish a small version of the flow, send a real message from a controlled test number, verify stored variables and routing, then expand the flow after the base path is stable.
Check these before assuming the platform is broken.
Open the workspace and turn the guidance into a live flow.
Once the account is connected and the first flow is tested, move back into the app and iterate from a working baseline instead of designing the perfect version up front.