WhatsApp Business
Send WhatsApp messages and templates to your customers from the application, through the official WhatsApp Business API, with the conversation logged in the system.
It covers what email cannot: confirming an appointment, warning that the technician is on the way, reminding a due date or sending a tracking link. These are messages read in minutes, not days.
Using the official API matters for two concrete reasons. The first is operational: templates are approved and messages go out without the risk of the number being blocked, which is what happens when personal accounts are used for bulk communication. The second is about the company: the number belongs to the business, not to the sales rep.
When somebody changes phones or leaves, the conversation with the customer stays where it was and whoever takes over can continue it. Each message's status (sent, delivered, read) is in plain view.
The channel people read
An email gets read in two days; a WhatsApp, in two minutes
That difference decides which channel to use for what. Some notices lose all their value if they arrive late, and they are precisely the ones that prevent the most hassle when they arrive on time:
- Confirming an appointment or a scheduled job.
- Warning that the technician is on the way, with an arrival window.
- Reminding a due date before it turns into an unpaid invoice.
- Sending a tracking link for a shipment or a ticket.
Messages are sent from the application, using prepared and approved templates, and the conversation is logged on the customer record so whoever attends to them later can read it.
Why the official API
The difference from using an employee's phone
This is the decision with the biggest consequences and the one usually taken without much thought. Sending from a personal account works for the first month and then fails in two different ways.
The number ends up blocked
Personal accounts are not designed for business communication. When volume rises or several recipients mark messages as unwanted, the number stops working, usually on the worst possible day. With the official API, templates are approved in advance and messages go through the channel intended for this.
The number belongs to the company, not the rep
This is the serious medium-term problem. If the customer relationship lives on one person's phone, it leaves with them: when they change role or leave, whoever replaces them starts from scratch and the customer notices. With a company number, the conversation stays where it was and whoever takes over continues it.
What stays on record
Delivery statuses and the conversation on the record
For each message you can see its status: sent, delivered and read. It looks like a detail and it settles a frequent argument, whether the customer received the notice or not, which until now was settled by persistence.
The full conversation stays on the customer record, alongside the rest of their history: emails, opportunities, quotes and jobs. Anyone on the team with permission can read it before calling, instead of asking around what was said last time.
And because messages are sent from the system itself, they can be triggered where things actually happen: when scheduling a job, issuing an invoice or changing an order's status.
Clearing things up
Frequently asked questions
Answers to what we get asked most.
Why use the official API and not an employee phone?
For two reasons. Operationally: personal accounts are not designed for business communication and the number ends up blocked when volume rises. And structurally: with the API the number belongs to the company, so the customer conversation does not leave with whoever changes phone or leaves the job.
What notices is it normally used for?
For the ones that lose value if they arrive late: confirming an appointment, warning that the technician is on the way with an arrival window, reminding a due date before it becomes an unpaid invoice, or sending a shipment tracking link.
Is the conversation logged?
Yes, on the customer record alongside the rest of their history: emails, opportunities, quotes and jobs. Anyone on the team with permission can read it before calling, instead of asking what was said last time.
Can I tell whether the customer read the message?
Yes, each message shows its status: sent, delivered and read. It settles the frequent argument about whether the customer received the notice, which until now was settled by persistence.
Communication and productivity
Announcements with read confirmation, tasks, reminders, chat, email and WhatsApp inside the same system your team already works in.
Announcements
A company announcement board that appears on every employee's dashboard when they log in, with read confirmation.
Tasks
Tasks assigned between colleagues with a deadline, a description and a reminder, attached to whatever they relate to.
Reminders
Scheduled alerts for whatever date and time you choose, one-off or recurring, delivered by notification and email.
Internal Chat
Instant messaging between system users, on a floating button available from any screen.
Webmail
An email client built into the application, with accounts per site and per user.
Suggestion Box
An internal channel for employees to submit improvement proposals, with their type and their handling status.