Loading…
Six steps from signup to a live conversation
Open a space, connect the business number, then reply from one inbox.
- 01
Client workspace
Create a dedicated workspace for your business.
- 02
Meta Embedded Signup
Connect your Meta Business through Embedded Signup.
- 03
WABA and phone number
Link your WhatsApp Business Account and number.
- 04
Webhook router
Route incoming messages and delivery events.
- 05
Bots and inbox
Automate routine requests and manage team replies.
- 06
APIs and analytics
Integrate your systems and measure activity.
What the provider layer includes
The company owns the number. The team replies from one inbox. Reminders go out from a message Meta has approved.
- A separate space for each business
Each business keeps its own number, inbox, templates, and the people who can reply.
- A number the business owns
Connect the WhatsApp business account from UlaloBots. The number stays with the company.
- Send and read from your software
On Scale, your software can send and read chats and use approved messages. Signed events can go to an address you control.
- The first reply you set
Guided chats cover the questions a shop, school, or clinic hears every day. A person can take over with the history.
Connect a number the company owns
A guided setup stores the business number in your team's space and checks that it is ready to receive chats. You can keep the WhatsApp Business app on the same number.
The first reply you set for questions you hear every dayBuild the first reply and the next steps for registration, orders, support, appointments, and applications. A teammate can take the chat with the history still attached.
Several people. One WhatsApp. Full history.Incoming WhatsApp threads show in the workspace. The people who need to reply can update the customer name and status, then answer while the thread is open.
Stop typing the same reminder to every customerTemplate Studio prepares the approved WhatsApp message. A live send stays blocked until that message is approved. Confirm a test in your workspace before you rely on a schedule.
Answer from what the business already knowsThe AI page uses sources you add in the same workspace as guided chats and the inbox. It does not replace Meta's rules for approved outbound messages, and it does not mean a person is on duty all night.
See message volume and how chats are goingThe analytics view and Control Center show workspace activity, WhatsApp delivery, and usage against the current plan allowance. They do not invent a performance score.
Send and read WhatsApp from your own softwareAuthenticate with an API key. UlaloBots stores only a hash of the key. Each outbound webhook has its own signing secret. This sends and reads WhatsApp. It does not drop every chat into a CRM for you.
Benefits of using UlaloBots on the official WhatsApp path
If the company number lives on one phone, or on a tool Meta did not approve, the chats can disappear with that phone or that number. UlaloBots connects the business through Meta's WhatsApp Cloud API. The protections below are Meta's, on that official path. Your team still replies from one inbox.
- Signal Protocol
- SOC 2 Type II
- ISO 27001
- 30-day limit
- Your Meta account
Is the clinic open tomorrow?
Yes. Appointments run from 8. A person on the team can take this chat with the history.
- Messages stay protected
- A customer message travels encrypted on WhatsApp. Cloud API decrypts it and forwards it to your business. When you reply, Cloud API encrypts the message with the Signal Protocol before it reaches the customer. Meta manages those keys on its servers.
- For Cloud API, Meta acts as a service provider for your business. It does not automatically use those WhatsApp messages to choose ads.
- Messages Cloud API stores are encrypted. Meta keeps them for at most 30 days, for delivery tasks such as resending, then deletes them.
- A path you can show a compliance team
- Meta reports SOC 2 Type II and ISO 27001 for Cloud API. Banks, clinics, and shops can point to Meta's own compliance center for those reports. These reports belong to Meta.
- Meta documents how Cloud API relates to laws such as GDPR and LGPD. Your business still meets its own duties under those laws.
- The number stays on an approved channel
- UlaloBots uses Meta's authenticated Cloud API. Tools that copy the WhatsApp app, or scrape the web version, sit outside that API. Meta can block those numbers. Spam and other breaches can still restrict a number.
- The connection uses Meta's published API. A copied WhatsApp screen is not what keeps the chats online when the app updates.
- You keep the Meta account and the Meta bill
- You connect your own WhatsApp business account from UlaloBots. The Meta Business Portfolio behind that number stays with you.
- You add the card that pays Meta inside your own Meta account. UlaloBots bills only the UlaloBots plan.
If only one phone has the chats, the business does not.
Connect a WhatsApp business number, set the first reply, and answer as a team with the full history.