Sign up
Campaigns

Reach the right people.
With their permission.

Send campaigns on WhatsApp, Messenger, Instagram and email from one place, to people who agreed to hear from you. One opt-out list is enforced on every send, Meta’s WhatsApp message fees are shown in AED before you launch, and the advanced parts — rich WhatsApp, email, journeys and customer activities — are Enterprise modules.

See plans and pricing

Included in Professional and Enterprise

One opt-out list, enforced everywhere

STOP, unsubscribe, bounces and complaints all land in the same list, checked on every send.

Rich WhatsApp and email from one place

Carousels, offers and coupons on WhatsApp; a block editor and your own domain for email.

Results in AED, not guesses

Cost, conversions and revenue from what customers did after the message.

Rich WhatsApp

Media card carousels, limited-time offers, coupons, catalog and multi-product messages.

Email campaigns

A block editor, test sends, one-click unsubscribe and sending from your own domain or mailbox.

Campaign safety

Opt-out list, STOP/START in English and Arabic, consent on the contact, quiet hours.

01

Four channels, one campaign screen.

A campaign is written once and sent on the channel your customers actually use, within each channel’s own rules.

  • WhatsApp campaigns use approved marketing templates; Messenger and Instagram campaigns are free inside the reply window and show AED 0.
  • The cost of a WhatsApp campaign is estimated in AED at the review step and reported per recipient from Meta’s own pricing after it runs.
  • Monthly recipients are set by your plan; opted-out customers are skipped at send time and listed in the warnings panel.
02

Create the message — rich WhatsApp or email.

Templates, cards and email blocks are built in the app, previewed as the customer will see them and test-sent before launch.

  • WhatsApp marketing templates with Change at Meta edits and named values; rich formats: media card carousel (2–10 cards), limited-time offer, coupon code, catalog message and multi-product message, with a Commerce catalog link per number.
  • Industry warnings before launch: clinic advertising approval, real-estate permit and licence numbers, retail promotion permits.
  • Email block editor — heading, text, image, button, PDF link and product cards — with desktop and phone preview, test send, full-size review and HTML download.
  • Send from our campaign address, from your own subdomain (DNS records checked), from your own mailbox (Google Workspace / Gmail, Microsoft 365 / Outlook, Zoho Mail or any SMTP server), or from your own Resend or SendGrid account.

Enterprise module · Email campaigns are also an Enterprise module

03

Target by what customers actually did.

Audiences come from your contacts and from Customer activities — the visits, appointments, repairs, purchases and enquiries recorded against each person.

  • Every contact with a valid address, people picked by hand, or a saved segment.
  • Filters for Age, Gender and “What they did”: had or never had an activity, in a period, where the details match.
  • Activities arrive from the inbox, from repair and retail sheets, from the ClinicGateway visits feed, or through POST /v1/activities.

Enterprise module

04

Automate with journeys and repeating campaigns.

Journeys send the next WhatsApp message by themselves when something happens to a customer, and stop the moment it is no longer needed.

  • Start a journey on a new activity, when an activity reaches a status (a repair is Collected), or N days before or after an activity date (a warranty end).
  • Steps: send a template, wait N days, stop if replied, read, not read, clicked or converted.
  • A journey stops on a reply, a later activity of a chosen type, an opt-out or the plan’s monthly limit.
  • Repeating campaigns run daily, weekly or monthly at a time in your workspace’s time zone; scheduled messages such as appointment reminders come from a connected system.

Enterprise module

05

Measure in AED, not impressions.

Results connect a campaign to what customers did afterwards, so a campaign is judged by visits, bookings and revenue.

  • Cost in AED from Meta’s per-message pricing, conversions within N days (visited, booked, bought, enquired, won) and revenue from activity amounts.
  • Retarget: turn Did not read, Clicked, Replied or Converted into a saved segment for the next campaign.
  • Email report: Opened (indicative), Clicked, hard and soft bounces, complaints and unsubscribes.
06

Stay compliant without thinking about it.

Consent, opt-outs and sending limits are built into every launch, on every channel.

  • One opt-out list per business: STOP and START replies in English and Arabic on WhatsApp, Messenger and Instagram, with a confirmation; a WhatsApp opt-out on any of your numbers blocks marketing on all of them, while a Messenger or Instagram STOP covers that channel.
  • Consent lives on the contact (Marketing section) with its history; launch warnings flag customers without recorded consent, people messaged too often, and sends inside quiet hours.
  • Optional quiet hours hold a campaign overnight (default 21:00–09:00 in your time zone) and resume it by themselves.
  • Email: one-click unsubscribe (RFC 8058) on every email; with our address, your verified domain or your Resend or SendGrid account, bounces and complaints go to the same opt-out list, senders warm up gradually and a campaign pauses itself when the bounce or complaint rate passes the limit. A mailbox sender returns no delivery reports.

How it works

  1. Pick the channel and audience

    WhatsApp, Messenger, Instagram or email; every contact, a hand-picked list or a segment built from activities.

  2. Build and test-send

    Template, cards or email blocks; preview on desktop and phone; a test send to yourself.

  3. Launch, watch the results

    Review the warnings and the cost estimate, launch, then read conversions and revenue — and retarget.

Included in Professional and Enterprise

For owners

Every message, accounted for.

Know what a campaign cost, who it reached, who opted out and what it brought in — and send the next one only to the people who should get it.

Start free trial Illustrative photo. Interface details use sample data.

Questions, answered.

Do we need consent before sending?

Yes. Your business is the sender and must have permission to message each person. The app records consent on the contact and warns you at launch about anyone without it; opt-outs are enforced on every send.

What happens when a customer replies STOP?

They are added to your opt-out list and skipped from every later campaign on that channel — on WhatsApp, across all your numbers. START undoes a STOP they sent themselves; opt-outs set by Meta or by your team stay.

Who pays WhatsApp fees?

Meta charges your WhatsApp Business account directly. The app shows the estimated cost in AED before launch and the actual cost per recipient afterwards.

Can we send email from our own domain?

Yes — from your own subdomain once its DNS records are verified, from your own mailbox by SMTP, or from your own Resend or SendGrid account. A mailbox sender does not return delivery reports, so bounces are not removed automatically.

What can pause a campaign?

Quiet hours, the plan’s monthly recipient or email limit, and — for email — a bounce or complaint rate above the limit. A paused campaign shows why and can be resumed.

Which plan do we need?

Campaigns are on Professional and Enterprise. Rich WhatsApp formats, email campaigns, journeys and repeating campaigns, and Customer activities are Enterprise modules; a Custom plan can add any of them.

Product screens are from the SM Gateway application with sample data. Cards and photos are illustrative.

Make it work
for your business.

Start free trial

Your privacy choices.

This website counts visits with Cloudflare Web Analytics, which sets no cookies. There are no advertising trackers. Essential preferences are saved in your browser. You choose whether to load the application’s chat service.

Disabling chat removes it from this page. It does not delete previously sent messages or storage held on the application’s domain.

Cookie details