TelediCONVERSATIONAL CHANNELSEspañol

Your template bot cannot write to the CRM. Ours can.

We build WhatsApp agents on Meta's official Cloud API, with persistent memory between sessions and write access to your CRM or ERP, scoped to the actions the job actually needs.

24 hMessaging window before Meta requires an approved template

02 / Why template chatbots go silent exactly when it matters

Why template chatbots go silent exactly when it matters

  • 01

    The 24-hour window, mishandled

    Meta allows free-form replies only within 24 hours of the customer's last message. After that the reply must sit inside an approved template. A bot that does not track that clock either stops answering or breaches Meta's policy, and both look identical to the customer.

  • 02

    Templates stuck in review

    Every message template goes to Meta for approval, and ambiguous wording or a badly labelled link sends it back. A template catalogue with no owner and no review process can hold an entire campaign for days.

  • 03

    Marketing opt-in with no audit trail

    The GDPR requires you to demonstrate when and how a contact consented to commercial messages. Template platforms rarely record that consent with the timestamp, channel and exact wording an inspection would ask for.

  • 04

    State lost between sessions

    If the customer closes the chat and comes back the next day, a bot without persistent memory asks for the same details again. From the outside there is no difference between a system that does not know something and one that simply never stored it.

  • 05

    Read-only integration

    Most template platforms read from the CRM but never write to it. An order confirmed over WhatsApp does not reach the ERP, so somebody re-keys it by hand in the afternoon — and the two records disagree until they do.

03 / How we build it

How we build it

  1. 01

    intake

    Signed and verified webhook from Meta's official Cloud API

    80 ms

  2. 02

    identity

    Contact resolved against your CRM or ERP by phone number

    40 ms

  3. 03

    memory

    Conversation state and relevant history retrieved for this contact

  4. 04

    reasoning

    Action decided: answer, query a system, or hand over to a person

    310 ms

  5. 05

    write

    Real update in the CRM or ERP — order, ticket or appointment, not a lookup

    220 ms

  6. 06

    template

    Approved template selected automatically once the 24-hour window has closed

  7. 07

    audit

    Every message, action and consent event written to the audit log

04 / Integrations

Integrations

  • Meta Cloud API
  • Salesforce
  • HubSpot
  • Dynamics 365
  • SAP
  • Zendesk
  • Odoo
  • Google Calendar

05 / Guarantees

Guarantees

< 24 h
Messaging window tracked per contactAutomatic switch to an approved template once it closes
100 %
Marketing messages with recorded consent
0
Details asked twice across sessionsPersistent memory per contact
Write access
Integration with your CRM or ERPScoped writes, not a read-only customer lookup

06 / Compliance

Compliance

  • Verifiable record of consent for every commercial message sent

    GDPR art. 6, lawful basis, and art. 7, conditions for consent

  • Conversation data hosted exclusively inside the European Union

    GDPR, chapter V

  • Every action the agent takes on your CRM or ERP is traceable to the message that caused it

    EU AI Act, traceability obligations, applicable from 2 August 2026

  • Logs and technical documentation kept in a form a market surveillance authority can inspect

    EU AI Act art. 99(4), penalties of up to EUR 15M or 3 % of global annual turnover

07 / Process

Process

  1. 1-2

    Conversation audit

    We read the existing transcripts and templates and mark the points where customers drop out or ask for a human. That is where the work is, not in the happy path everyone already demos.

  2. 2-3

    Templates and consent design

    Templates drafted for Meta approval, and an opt-in flow whose record holds up on its own: timestamp, channel and the exact wording the contact accepted.

  3. 3-6

    CRM or ERP integration

    Read and write integration with your system of record, with the write scope agreed field by field rather than inherited from a full-access service account.

  4. 6-8

    Memory and human handover

    Persistent per-contact memory, and explicit rules for when the agent stops and hands the conversation to a person with the full history attached.

  5. ongoing

    Operation

    We track template approval rate, latency and handover volume, because those three numbers are what tell you whether the agent is helping or quietly failing.

08 / Frequently asked questions

Frequently asked questions

How long does Meta take to approve a message template?
Anywhere from a few minutes to 48 hours, depending on the category. We draft templates in the form Meta approves first time most often, so a campaign does not depend on resubmissions.
What happens if a customer writes after the 24-hour window closes?
The system detects that the free-form window is closed and replies with the matching approved template, so the customer never sees a gap in the conversation.
Can the agent confirm an order, or only look one up?
It writes to your CRM or ERP: confirming an order, booking an appointment, opening a ticket. It is an integration with a scoped write permission, not a read-only layer over the customer record.
How is consent for commercial messages handled?
Each opt-in is stored with its timestamp, the channel it came through and the exact text the contact accepted, so the record can be produced in a data protection inspection without reconstructing it from screenshots.
Can we keep the number we already use in WhatsApp Business?
It depends on whether it is still on the standard app or already migrated to the official Cloud API. If it is not migrated, that migration is step one of the project.
What does the agent do when it cannot answer?
It hands the conversation to a person with the full history attached, rather than repeating a generic reply or inventing one. The threshold for handing over is set with your team, not by the model.
What does sending WhatsApp messages cost?
Meta charges per conversation by category and country, billed to you directly. Our development cost is separate from that rate and does not scale with your message volume.

09 / Related services

Related services

10

Tell us which process to fix

Describe the process and the systems behind it. You get back a technical proposal — architecture, timeline and acceptance criteria — not a service catalogue.

Email hola@teledi.ai