Service · Meta business platform

WhatsApp and Instagram integrations

Your company already serves customers over WhatsApp and Instagram. The problem is usually the same: those conversations live outside the company's systems, spread across phones and separate apps, with no history, no access control and no link to the CRM, the ERP or the booking calendar.

Praeda connects the two. I build and operate, on behalf of your company, the integration between the systems you already run and your own WhatsApp Business and Instagram professional accounts, using the WhatsApp Business Platform and the Instagram Messaging API. The account is yours, the phone number is yours, the data stays in your infrastructure. I am the technical provider who makes it work and keeps it working.

What I build

The software layer between Meta and your business: it receives the messages, puts them inside your system, sends the reply back and records everything.

  • Inbound messages over webhooks, with queueing and retries, so nothing is silently dropped
  • Outbound replies, media, buttons and Meta-approved message templates
  • A single inbox for your team, or integration with the one you already use
  • Wiring into the CRM, ERP, calendar, billing or internal system that owns the process
  • AI-assisted replies where it makes sense, always with handoff to a human

What I run afterwards

A messaging integration does not end on launch day. It needs someone watching what Meta answers back.

  • Monitoring of delivery, failures and response times
  • Tracking of your number's quality rating and messaging limits
  • Submission and upkeep of message templates
  • Keeping up with platform version and policy changes
  • Audit trail of who replied what, and when

How it works, from the first call to live

Same format as every other Praeda engagement: scope and deliverable defined before we start.

  1. Design and account connection

    I map the customer service process you already run and design the flow. Your company connects its own account through Meta's official onboarding flow, with the phone number and the business portfolio under its own name. I run it technically, but ownership never leaves your company.

  2. Building the integration

    Scope, architecture and price in writing before the first line of code. The integration is written for your process, runs in your cloud account, and the code lives in your company's repository from the first commit.

  3. Operation and support

    Once it is live, I watch delivery, failures, number quality and platform policy changes. Monthly format, for an agreed period. If you would rather run it yourself, I hand it over documented and step out.

No per-seat subscription and no platform licence. You are hiring engineering, not a black box.

What companies use it for

Customer service with history

Every WhatsApp conversation and every Instagram direct message and comment lands in the same place, tied to the customer record. The team replies from inside the company's system, and the conversation does not disappear when someone changes phones.

Transactional notifications

Order confirmations, appointment and booking reminders, delivery updates, payment notices. Triggered by the system that already holds the data, through an approved message template, to people who opted in.

Booking and self-service

Customers book, reschedule or cancel inside the conversation, against the company's real calendar. Whatever automation cannot resolve goes to a person, with the context attached.

Lead qualification

People arriving from an ad or from the Instagram profile are greeted, qualified and routed to the right team, with the record landing in the CRM without manual typing.

Recurring stack on this kind of project: TypeScript, Node.js, Python, FastAPI, PostgreSQL, Next.js and AWS (Lambda, API Gateway, SQS, DynamoDB, ECS).

What data I handle, and what I do with it

A messaging integration touches end-customer conversations. So it is worth spelling out what comes in, what it is used for, and what never happens.

What the integration receives from Meta

Only data that belongs to the client company itself, and only what the conversation requires:

  • The messages end customers send to the company, and the replies the company sends back
  • The phone number on WhatsApp, or the profile identifier on Instagram, of the person who wrote in, plus their display name
  • Delivery, read and failure status for each message
  • Account identifiers and credentials belonging to the company, needed to keep the connection alive
  • Conversation metrics, used for the company's operational reporting and cost reconciliation

What that data is used for

To deliver the message into the client company's system, show the conversation to its team, send the reply back to the end customer, trigger the notifications that end customer opted into, and produce the company's own operational reports. Nothing beyond that.

The data stays in the client company's infrastructure, in its cloud account, under its credentials. Retention is decided by the client, not by me. My own access is the minimum needed to build and operate the integration, it is logged, and the client can revoke it at any time without depending on me.

What never happens here

  • I do not sell, rent or share this data with any third party
  • I do not use one client's data to serve another, or to build a database of my own
  • I do not use end-customer conversations to train any AI model of mine
  • I do not use this data for advertising, mine or anyone else's
  • I do not run bulk messaging to purchased lists, or to people who did not opt in

Who owns what

The business portfolio, the WhatsApp Business account, the phone number and the Instagram professional account belong to the client company, under its own name and its own agreement with Meta. Praeda acts as the technical provider, on that company's behalf, with the access it grants and for as long as it wants. No asset is held in my name, and there is no scenario where your company needs my permission to run its own channel.

In practice this means the work follows Meta's business messaging policies and the data protection law that applies to your case, including Brazil's LGPD and the GDPR when end customers are in Europe. Contact only with consent, opt-out honoured, purpose declared.

Tell me your case

Write two lines about what your company needs to solve on WhatsApp or Instagram and what runs today. I reply with a first technical read and a suggestion of where to start, with no commitment and no commercial proposal at that stage.

Based in São Paulo, UTC-3, with daily overlap with North American and European business hours. Meetings and technical documentation in English or Portuguese. The contract is with Praeda Ltda, a registered Brazilian company, invoicing international clients directly.