Cloud API onboarding
We register your number on the Cloud API, submit business verification with Meta, configure the display name and webhooks, and confirm delivery is working before anything else is built.
Most customers message after hours and get silence until morning. We put your business on the official Cloud API so enquiries get answered, tracked and handed to the right person.
In Oman, WhatsApp is where conversations actually happen. A customer sends a photo of a menu, a plate number, a quotation request or a payment receipt, and expects an answer. Handling that by hand means one person holding a personal phone, no record of what was agreed, and no way to tell at 7pm whether a lead has already been answered. We move that conversation onto the official Business Cloud API so it becomes trackable work, not a private habit.
The work starts with the unglamorous part: your display name, business verification documents, phone number hygiene and message templates that Meta will actually approve. We build opt-in lists that respect consent, write templates for the twelve or so notifications you genuinely need, and configure a shared team inbox with agent assignment, internal notes and handover between shifts. Everything syncs into your CRM so a WhatsApp enquiry appears in the same pipeline as a website form.
Every engagement includes documentation, handover and a named contact.
Six pieces that turn WhatsApp from an unmanaged personal phone into a channel with measurable response times.
We register your number on the Cloud API, submit business verification with Meta, configure the display name and webhooks, and confirm delivery is working before anything else is built.
Contacts are collected with clear consent at the point of purchase, on your site or in-store form, then stored with timestamp and source. Non-consented numbers are filtered out automatically.
You get an approved template set for order updates, reminders and confirmations, plus interactive buttons and lists inside the chat so customers reply with one tap instead of typing.
Booking confirmations, order shipped, payment received and invoice ready messages fire automatically from your system, triggered by real events rather than a manual send.
Every conversation lands in one queue with agent assignment, internal notes visible only to staff, transfer between agents and a full history that survives a phone change.
Leads from Meta lead ads arrive in WhatsApp and land in your CRM with the campaign source attached, so ad spend, conversation and follow-up sit in the same report.
Messages go out only to people who opted in, through templates Meta has approved. That protects your sender number from the restriction and ban that ruins unverified setups.
Assignment rules stop two agents replying to the same lead, and an internal handover note carries the context when a conversation moves to another shift or department.
Flows detect the language of the incoming message and respond in kind, including the mixed Arabic-English style customers in Oman and the wider GCC actually use.
The bot handles FAQs and status checks, then escalates on sentiment, repeated questions or any request a machine should not answer alone. It hands over with full context.
We test against Meta test numbers and a limited opt-in list first. When messages, windows and templates behave as expected, we open the channel to the full customer base.
Taking table and event bookings, confirming orders by message, and pushing daily specials to a consented customer list.
Confirming stock availability, sending order updates and reservation messages without staff repeating the same answer all day.
Appointment confirmations, reminder messages before visits and refill follow-ups, with questions routed to a person.
Qualifying enquiries, sending viewing confirmations and property brochures to opted-in leads instantly after an ad click.
Proof of delivery photos, arrival notifications and rescheduling requests handled automatically through the driver route.
Filling slots from a shared calendar, sending reminders that cut no-shows, and confirming deposits before the appointment.
Five stages from raw number to a channel the whole team can work from.
We assess your existing number, register it on the Cloud API and submit business verification to Meta. This is the step with the longest lead time, so it starts first.
We map which messages you need, write them in Arabic and English, and submit them for approval while opt-in capture is added to your site, form or till point.
We build the automated answers, escalation rules and the shared team inbox with assignment and handover, then connect webhooks to your existing systems.
We start with a limited opt-in audience, then widen. We watch delivery rate, response time, template rejections and opt-out rate weekly and adjust copy and timing.
Conversations, contact details and campaign source flow into your CRM so the sales pipeline reflects everything customers send, with reporting on response and conversion.
The phone app has no API, no shared inbox and no record of which agent answered. Only the Cloud API connects to your CRM, supports automation and keeps the conversation when someone changes role or leaves. If your volume is small and one person covers it, the app may genuinely be enough.
Typically a few days to two weeks, and it depends entirely on Meta, not on us. That is why verification is the first task. Business documents, a matching business email and a live website or landing page all speed it up considerably.
Not if you stay inside the policy: opt-in before you message, use approved templates outside the 24-hour customer service window, and respect STOP requests immediately. We configure opt-out handling on day one. Accounts can still be reviewed, so we keep your message quality and complaint rate low.
They see your business name, not a bot label. Inside the customer service window, replies can be free-form; outside it, you need approved templates. You choose how much is automated, and anything complex is escalated to a named agent with the history attached.
Meta charges per conversation, based on the customer country and message category, and there is no monthly platform fee from us. Hosting for the integration is small, typically a modest server or existing Laravel host. We show you the expected monthly conversation volume and the approximate Meta charge before you commit to anything.
Usually yes, if the number is eligible and not currently registered to another Cloud API account. We check eligibility during the first call. In some cases we register a new number and migrate the contacts across, which we explain before anything changes.
Corporate sites, Laravel web apps and redesigns built for Muscat businesses. Arabic and English, mobile fast, SEO ready. Talk to Dastgir IT Services.
Map your processes, then automate the slow ones with AI agents, n8n workflows and document extraction. See a working pilot before rollout. Talk to us.
Connect your ERP, payment gateways, and cloud apps with stable API and webhook integrations built from Muscat for Oman and GCC businesses.
A few details are all we need to get started. Fields marked * are required.
Send us your WhatsApp number and business name. We will tell you whether it is eligible, what approval needs, and what it costs before you sign anything.
We reply during Oman business hours, Sunday to Thursday. · +968 9651 5039 | +968 9355 7155
50+
Websites Delivered
10+
Mobile Apps
100%
Client Satisfaction
Oman Focused
Local Support