Skip to content
Solution · WhatsApp inboxSolutions

WhatsApp, Instagram and Messenger in one inbox, built for your team

Alif Logix builds WhatsApp systems directly on Meta’s WhatsApp Cloud API, with Instagram and Messenger in the same inbox. The system runs on your own server, and every enquiry can keep the source it came from.

What we build

WhatsApp inbox & automation

  • One inbox for every channel

    WhatsApp, Instagram and Messenger conversations arrive in one team inbox instead of on separate phones. Several WhatsApp numbers can run side by side, each approved by Meta under your company name, and every contact is kept with its full history, a simple WhatsApp CRM that can be exported.

    In use

    A consultancy in Kuwait runs its WhatsApp, Instagram and Messenger enquiries through one inbox on its own server. Read the case study: WhatsApp, Instagram & Messenger inbox

  • Automated flows and first replies

    Each number can run its own flow: the questions a new enquiry is asked, the answers that route it, and the away message outside working hours. AI-assisted replies suggest an answer or translate a message, and your team decides what is sent.

    In use

    Flows per WhatsApp number, an away message outside hours, and suggested and translated replies for the team. Read the case study: WhatsApp, Instagram & Messenger inbox

  • A mobile app for staff

    Staff reply from an Android app with the access they need, so an enquiry that comes in after the office closes is not left until the morning.

    In use

    An Android app for a consultancy’s staff, working on the same inbox and contact records as the office. Read the case study: WhatsApp, Instagram & Messenger inbox

  • Templates and broadcasts

    Approved message templates and broadcasts to contacts who have opted in, sent from the same system that holds the conversations, so a campaign and its replies are in one place.

    In use

    Template messages and broadcasts sent from the consultancy’s own WhatsApp Business account. Read the case study: WhatsApp, Instagram & Messenger inbox

  • Every enquiry can keep its source

    The ad, page or link that started a conversation can stay with the enquiry, so marketing can be judged by cost per booking by source instead of by clicks. More on tracking each enquiry back to the ad and on marketing measured by bookings.

    In use

    This website does the same for its own contact form: campaign tags, click id and landing page travel with each enquiry.

Try it live

Try the WhatsApp inbox

Follow one enquiry through a team inbox: the number’s flow asks its first question and routes the answer, and the contact record keeps the full history and where the enquiry came from. Then edit a suggested reply and send it, switch to out of hours, and see the same thread in the staff app.

What you can try

  • Answer the flow’s first question and see the enquiry routed to Sales
  • Open the contact record: its history and where it came from
  • Edit a suggested reply and send it
  • Switch to out of hours, then open the staff app
WhatsApp inboxDemo · sample data

A demo with made-up names and numbers. It shows the kind of system we build, not a client’s system. Nothing you do here is sent or saved.

  1. Step 1 of 4: A new enquiry arrives and the number’s flow routes it
  2. Step 2 of 4: Open the contact record: its history and its source
  3. Step 3 of 4: Take a suggested reply, edit it and send it
  4. Step 4 of 4: Switch to out of hours, then open the staff app

InboxYour business (demo)

New enquiry
  • WhatsApp
  • Instagram
  • Messenger
  • Sara M.nowHi! Is Thursday 11:00 free?WhatsApp · Sales line(open, unread)
  • Tom B.4mThanks, see you then!Instagram
  • Lena R.12mCould you send a quote?Messenger
  • Omar K.1hBooked for Friday, thank you.WhatsApp · Support line
  • Priya S.2hWhat are your opening hours?Instagram

Sara M.WhatsApp · Sales line

  1. Sara M.: Hi! Is Thursday 11:00 free?
  2. Flow · automatic: Thanks for your message! What can we help with?
  3. Answer as the customer:

Capabilities

WhatsApp inbox

  • One inbox
  • Automated flows
  • Staff app
  • Templates & broadcasts
  • Source tracking
Build log

Recent builds

details on request

  1. Booking site + WhatsApp line

    Umrah transport · Saudi Arabia

Case files

Work we have shipped

Details on request. Images are illustrative.

Illustrative render: WhatsApp, Instagram & Messenger inbox
Illustrative

Work / Consultancy · Kuwait

WhatsApp, Instagram & Messenger inbox

  • AI & automation
  • One inbox for every channel
  • Automated flows
  • Staff app
  • Templates & broadcasts

A consultancy in Kuwait runs its WhatsApp, Instagram and Messenger enquiries through one inbox on its own server.

Process

How a build goes

  1. Step 1 of 3

    Scope, in writing

    Which numbers and channels, which flows, who in the team needs access, and what the inbox must connect to. Two pages, agreed before anything is built. What goes in a written scope.

  2. Step 2 of 3

    Connect and build

    Your WhatsApp Business account is connected to Meta’s Cloud API, the inbox and flows are set up on your server, and your team starts using it on real conversations early.

  3. Step 3 of 3

    Run and improve

    A monthly care plan keeps it running and adds the next flows and reports as the team asks for them.

Compare

A subscription inbox or a system built for you

A subscription inbox is enough when

  • one or two people answer messages
  • the conversation ends in the chat and nothing needs updating elsewhere
  • the vendor’s standard flows fit how you qualify an enquiry

A built system is worth it when

  • enquiries must land in your own booking, job or CRM records
  • you want your own questions, routing and reports
  • per-seat fees on top of Meta’s message charges keep growing with the team
  • you want the conversations and contacts on your own server

The first WhatsApp inbox we built replaced a third-party subscription: going direct to Meta’s Cloud API removed the middleman’s markup (Meta still bills per message) and put the conversations and lead data on a server the business controls.

Questions

Questions we get asked

  • Is it built on Meta’s official API?

    Yes. The inbox connects directly to Meta’s WhatsApp Cloud API, the same official API that subscription inboxes use.
  • Can Instagram and Messenger come into the same inbox?

    Yes. WhatsApp, Instagram and Messenger conversations arrive in one inbox with one contact record.
  • Can staff reply from their phones?

    Yes, from an Android app on the same inbox.
  • What does Meta charge, and what do you charge?

    Meta bills WhatsApp messages directly to your WhatsApp Business account at its published rates, separately from us; see Meta’s WhatsApp pricing. Our work is priced per project in a written scope, with an optional monthly care plan.
  • Why not just use a subscription inbox?

    For many teams a subscription inbox is enough. A built system is worth it when the conversations need to reach your own booking, job or CRM records, when you want your own flows and questions, or when you would rather not pay a per-seat subscription on top of Meta’s charges. The same question for any software: when custom software beats a subscription.
  • Where are you based?

    Alif Logix works from four locations: Lahore (Pakistan), Southall (United Kingdom), Pampanga (Philippines) and Sharjah (UAE). We work with clients anywhere, in writing and on calls.
Contacts

Tell us what is slow, manual or invisible.

We reply to every enquiry within one working day.

Your message is emailed to us and used to reply to you. See our privacy policy and terms.