WhatsApp Business API Setup and Automation
Customers use WhatsApp to ask for prices, send documents and request appointments. You can answer routine questions automatically, route other enquiries to the right person and keep the conversation with the customer record. I set up your WhatsApp Business API around that workflow: a shared inbox, reliable information sources, automated replies and clear handover points for your team.
Discuss your requirements · Explore the hotel pricing and booking scenario
What is the WhatsApp Business API, and when do you need it?
The WhatsApp Business API is the official connection for sending and receiving business messages through software. Meta’s hosted connection is called Cloud API. A shared inbox, customer database and AI are separate components built around it; opening an API account does not create a working customer service operation on its own.
The WhatsApp Business app may be enough if saved replies and manual follow-up meet your needs. Consider an API setup when a message must be attached to an order, assigned to a colleague or used to start a process in another system. Direct development and provider-based integration are both options. Meta’s integration options.
| Requirement | Setup approach |
|---|---|
| Answer common questions | An approved information source and human handover. A live inventory connection is not required. |
| Show current status | Read access to an order, calendar or hotel system. No definitive status is reported without access. |
| Complete a transaction | Read and write access, customer approval and verification of the result. Repeated messages must not create duplicate transactions. |
For the technical reasoning behind the AI connection, read my WhatsApp AI integration guide.
What can your WhatsApp number do?
| Customer enquiry | Workflow I can build |
|---|---|
| “How much does this service cost?” | Share approved service information and collect the details needed for a tailored quote. |
| “What is happening with my order or booking?” | Retrieve the relevant record from a connected system after identity and access checks. |
| “Do you have a suitable appointment?” | Offer available slots from an accessible calendar and confirm the result of the booking. |
| “Can I send the document here?” | Attach supported files to the conversation so your team can find them in the customer record. |
| “I approve the proposal.” | Record the approval against the specific proposal and version, then pass it to the next step. |
| “I would like to speak to someone.” | Hand the conversation to your team and pause automated replies while a person responds. |
Each workflow has its own scope. Your software’s access options, the quality of its data and how your team works determine what can be connected.
What the setup includes
A business-owned API connection. I check the number and business account, then configure the official WhatsApp Business Platform connection. If you need to migrate an existing number or retain app access, I check eligibility first. Your business retains control of its account and number.
A shared inbox and customer records. Authorised staff can see conversations, earlier messages and supported attachments in one place. Internal notes are separate from customer replies, and conversation ownership is visible.
Reply rules based on your business. Stable information comes from content you approve. Changing information comes from systems you authorise. AI can interpret a question and write a clear response; it does not become the source of prices, stock or booking status. If the source is unavailable, the workflow hands over to staff.
Testing and an operational handover. I test missing information, unavailable systems, repeated messages and staff takeover as well as successful replies. The agreed scope identifies how the team will use the inbox and who will keep the information current.
What are the steps in a WhatsApp API setup?
- Account and number: I check business portfolio permissions, the number’s existing registration and its verification method. A migration requires a downtime and rollback plan.
- Official connection: The chosen onboarding route connects the number, application permissions and incoming message events. Credentials stay out of visitor-facing code.
- Shared inbox: I set up staff access, conversation assignment and internal notes. Incoming messages and delivery status events are recorded separately.
- Information and business systems: Each answer is tied to a source. CRM, calendar or booking connections are tested with the intended permissions.
- Permission and reply flow: Initial replies, template requirements, opt-out handling and human handover are defined. Marketing permission stays separate from approval of a specific job.
- Phone testing and handover: I check delivery to a real phone, replies appearing in the correct conversation and staff taking over. Operating notes, maintenance scope and responsibilities are included.
To begin, I need the authorised account contact, the intended number, your software names and an example customer conversation. I assess timing after checking the number, platform approvals and system access.
Example: from a hotel rate enquiry to a booking request
A guest provides dates and party size. Where a suitable integration is available, the workflow checks the hotel’s rates and availability, explains the options and collects the request. Confirmation requires a successful response from the booking system or an authorised member of staff.
Read the pricing, availability, booking and reception handover scenario.
I also use catalogue, report and approval demos with an inbox connection on my own +90 850 304 43 65 number. Open the demo menu on WhatsApp. That menu demonstrates my own services in Turkish; the hotel workflow is a separate illustrative scenario.
WhatsApp workflows by business type
The job after “reply to the message” differs by business. A barbershop appointment links a service and slot to a calendar. Hotel guest communication routes arrival and transfer requests to reception. Technical service tracking gives each fault a job reference and status. Agency proposal approval connects a client’s decision to the right PDF version. Each page separates the illustrative workflow from the integrations needed for a real installation.
Current messaging rules and costs
Checked on 24 September 2026: free-form replies use the 24-hour window following a customer message; outside it, approved templates are required. Obtain permission for subsequent contact, honour opt-outs and provide human escalation. Meta’s messaging policy, updated 23 September 2026.
Setup, hosting, maintenance and any AI usage are separate costs. Meta’s messaging charges depend on the recipient’s market and message category. Its current pricing makes service messages and eligible utility messages within the customer service window free; this does not make the whole solution free. My proposal states the usage assumptions alongside Meta’s current pricing.
How is the WhatsApp API cost calculated?
The proposal separates one-time implementation from ongoing operation. Implementation depends on the integrations, workflow scope and data preparation. Operation depends on the inbox, hosting, maintenance, model usage and chargeable messages.
A number answering incoming price enquiries has a different cost profile from one sending approved campaign templates to several countries. A cost estimate needs recipient markets, approximate monthly volume, message purpose and connected systems. Meta charges are shown separately from my development and maintenance work.
How we start
We choose one recurring conversation: a price enquiry, appointment request or order check. We identify its information source and define what counts as completion. I then build and test a focused workflow under realistic conditions before adding further use cases.
For the initial scoping, I need the current number’s setup, the name of your business software and an example workflow. You do not need to share private customer records through a public channel.
Contact me about WhatsApp API setup. For hospitality, see the hotel booking scenario. For reporting and internal tools, explore custom web apps for your team.
I am Oğuz Erol, and I design and implement this service. Experience with my own number informs my implementation decisions. The hotel illustration is not a customer case study. I checked the platform information against official sources on 24 September 2026.
Frequently Asked Questions
Is this just an automated greeting?
No. Depending on the scope, I can connect the shared inbox, customer records, files, business software and staff handover. If you only need prepared replies, I keep the project focused on those.
Does every reply need AI?
No. Menus, status checks and approval records can follow explicit rules. I add AI where understanding a freely written question or explaining retrieved information provides a useful benefit.
Can customers complete a form inside WhatsApp?
WhatsApp Flows supports structured information collection within a conversation. Where appropriate, I can use it to collect dates and preferences. Connecting that form to your hotel or CRM is a separate part of the implementation. Meta’s WhatsApp Flows overview.
What if our software has no API?
I first check for a reliable access or export option. If live data is unavailable, the workflow collects information and routes requests to staff. It does not promise current stock or a confirmed reservation.
Do we have to change our number?
That depends on the number’s current registration and the chosen setup. I check migration, verification and existing app use before promising that a number can be retained or used alongside the app.
How do I work?
Work-hour packages
Tell me about your website and what you need on WhatsApp or by phone; we agree on a work block of somewhere between 5 and 40 hours and I start doing what is needed. What you get is not a calendar window — it is net working hours spent directly on your business. I can use 40 hours working three days straight, or deliberately spread it out and finish it over a year — whatever the work calls for. I do not spend my time estimating how long something will take, I spend it doing the work; every hour I spend has a lasting result on your site. We keep going for as long as you find it useful.
Why not monthly?
Is 40 hours a week?
On a fixed monthly fee both sides are watching the wrong thing: you watch a fixed cost, the other side watches how many more contracts like this they can line up. Working by the hour puts us both in front of the same thing — the real value of the work that got done. I know not having an upfront answer to "how much will this cost in total?" is the natural cost of this model. But instead of paying a fixed fee for months to a setup that is not producing results, you only pay for the qualified time spent on your work — and you see exactly where that time went, start to finish. That is why my clients keep coming back.