WhatsApp through Wazzup
A separate Wazzup channel type with a different connection mechanism from WABA. The WABA template window is not its sending model; tariff, account and channel rules still apply.
SABSUS · WhatsApp + Wazzup
Keep the WhatsApp conversation.Connect the work behind it.
Connect messages with customer history, the responsible team and the next action in SABSUS. Choose the appropriate Wazzup connection before designing reminders, repeat conversations or an AI handoff.
Choose the connection
Two WhatsApp routes. Different conditions.
SABSUS describes a technical partnership with Wazzup. The actual connection, features and commercial terms still need to be agreed for your account.
WhatsApp Business Platform
WABA follows Meta’s messaging rules. Outside the 24-hour window, use an available approved template with the required consent and channel charges. A template send alone does not open free-form messaging.
Continue with permission
A follow-up needs a valid way to send
Compare the two timing examples below. The WABA example assumes its template is already approved. If the right template, consent or permission is missing, the team must resolve that before a real message is sent.
Follow up when your business needs to.
Revisit an enquiry after three days. Remind someone about a booking. Tell them a product is back in stock. Your team continues from SABSUS while the configured workflow handles the available sending method.
- Customer history and commitments at hand
- The right number, channel and owner
- Less manual work tracking the messaging window
Hello! The bouquet you liked is available again. Shall we prepare an order for tomorrow?
From a number to a workflow
Connect the channel and the responsibility
Confirm the account
Choose the connection type and numbers. Confirm provider availability, account requirements and the applicable plan.
Match the customer
Use available contact data to link the conversation to the customer record. A similar name alone is not identity evidence.
Set the next action
Decide whether the scenario prepares an order, booking or task. Define the responsible team and the limits of automation.
Test the boundaries
Review missing data, unavailable templates, repeated actions and handoff. Confirm outcomes in the real system before expanding.
Before live messaging
Define what the team can rely on
- Connection type, approved numbers and provider requirements
- Customer consent, template availability and applicable message charges
- Customer matching, responsible staff and escalation rules
- Separate order, booking and payment confirmation states
Use these as acceptance criteria; they are not a record of checks already completed.
Your next step
Bring the conversation you want to keep moving
Tell us which numbers, team and customer actions matter. We can discuss the Wazzup connection, consent, templates and handoff for your workflow.
Tell us about the process. Please do not include passwords, API keys or customer records in this inquiry.
Explore the sample inbox
The next teammate sees what was already agreed
Try the sample conversations and the human handoff. The visible customer, order and payment states are illustrative; these controls do not contact customers or change your CRM.
Customers and enquiries
Irene · bouquet
WhatsApp → order → deliveryThe customer returns after discussing a bouquet. Preferences and delivery date are saved in CRM.