What's new in meiti

13 October 2026 Telephony

Caller ID with meiti Call: see why a number is not available

"Change" on the caller ID now stays available for "meiti Call" too. Numbers meiti Call on this device cannot show are listed under "Not available with meiti Call on this device". Tapping one picks the number and switches to "Via phone number".

Why it matters

Until now the choice simply disappeared. Now you see the reason and still reach the customer with your number in one tap.

How to use it

1. Open "Call", pick "meiti Call" and tap "Change" on the caller ID.
2. Tap a number under "Not available with meiti Call on this device" – the call then runs via phone number with that caller ID.
3. Want your number to work everywhere? Tap "Request porting" below it. Our team will be in touch.

13 October 2026 App

"Draft" tag in the request list

When a conversation holds an unsent draft – a reply suggested by your assistant or a text someone on your team started – its row in the list shows a small "Draft" tag next to the name.

Why it matters

Prepared replies no longer get lost: you see right in the list where all that's left is to check and send.

How to use it

1. Open a conversation tagged "Draft" – the draft is waiting above the message field.
2. Send or dismiss the draft. Back in the list, the tag is gone.

13 October 2026 Telephony

"Phone system" instead of "Voicebot settings", recording as a switch

The phone settings are now called "Phone system". You pick the recording there and when calling with one switch: "Off", "My side" or "Both sides". When calling, the pencil next to the sentence your customer hears leads straight to the phone system.

Why it matters

The page covers more than the assistant – also the calls you hold yourselves. And whoever wants to change the announcement finds it with one tap.

How to use it

1. Open "Call" and expand "Dokumentation". Pick the recording with the switch.
2. Tap the pencil next to the sentence your customer hears – the phone system opens.

12 October 2026 Integrations

"Open in CRM" without a CRM integration — right next to the number

You can now always enter the link to the contact and the link to the case, even without a connected CRM and without the customer or case number switched on. In the ticket each number appears only once: with its label and an open icon next to it that opens exactly this record in your CRM. The example links shown while you enter one are now fully readable.

Why it matters

Many teams work with a CRM that meiti does not connect directly. With your own link you still jump from the ticket to the customer or job in one tap — no sync, no searching.

How to use it

1. Open "Settings" → "Setup & operations" → "Connected systems" → "CRM & industry software".
2. Under "Numbers", tap "Link to the contact" or "Link to the case" and enter the link with {nummer} where the number goes — or take an example and adapt it.
3. In the ticket, tap the open icon next to the customer or case number.

12 October 2026 Telephony

Team call: an unanswered colleague is covered by their own ring group

If a colleague doesn't answer an internal team call, their own ring group rings next, target by target — as with customer calls. Only the meiti app of the colleagues in the ring group rings, never a phone number. If they decline the call, it ends as before.

Why it matters

Your own ring group says who steps in when someone can't be reached. That now also applies when the team calls each other.

How to use it

1. Open the member → create "Eigene Rufgruppe" and add colleagues.
2. Call the colleague from "Internal" and don't answer: after about 30 seconds the app of the next person in the ring group rings.

12 October 2026 Telephony

On the phone your assistant uses "du" throughout when you set "Du"

If "Anredemodus" is set to "Informell (Du)", every fixed sentence on the phone now uses "du" too: the "leave a message after the beep" line, the announcement before a forward ("ich verbinde dich mit …"), questions for name, number or address, appointment questions, the mailbox prompt and the classic phone menu. The AI's own answers follow the setting as well. Until now these sentences always used "Sie". Each of them now also exists in English for English-speaking callers, as do the ticket's system lines about forwards.

Why it matters

A call held in "du" that switches to "Sie" halfway through sounds like a machine.

How to use it

1. Under "KI-Basis und Wissen" set "Anredemodus" to "Informell (Du)" and leave "Anrufer kann eine Nachricht hinterlassen" on for the assistant.
2. Call and end the conversation: before the beep you hear "Nach dem Signalton kannst du noch eine Nachricht hinterlassen."
3. Ask to be forwarded: the announcement says "Einen Moment, ich verbinde dich mit …".

11 October 2026 Telephony

"Caller left no info" instead of an AI summary when the caller says nothing

If a caller hangs up before saying anything, meiti no longer summarises the call. The card in the ticket is then simply called "Caller left no info". "Nachlesen · n" on the card now counts the caller's messages plus the call's system lines, no longer the sentences of your team or your assistant.

Why it matters

A summary of your own greeting says nothing. At a glance you see who tried to reach you and how much the caller had to say.

How to use it

1. A tap on the card opens the call directly. More options (e.g. "Löschen") sit behind "…", a long press, or a right click on the computer.

11 October 2026 App

Alerts by email too

Alert skills now send emails too: on top of the push notification to the email address in the meiti account of each notified member — or, instead of the members, to an address outside the organisation. meiti sends it itself; there is no sender to set up. The bottom of every email says which inbox and skill it comes from, how to stop it and where to get help.

Why it matters

Not everyone has the app open or wants alerts by SMS. People who live in their inbox now get the alert there — and partners without meiti access can be reached by email too.

How to use it

1. "Settings" → "AI assistants" → pick the assistant → open the alert skill → "How your team finds out" → "Additional channel" → "Email".
2. For someone outside: in the skill, "Notify someone outside the organisation", choose "Email" as the channel and enter the address.

More in the docs →

11 October 2026 Telephony

Via phone number: meiti rings your phone or desk phone first

With "Via phone number", under "meiti calls you at" you can now pick not just a number but also your phone with the meiti app or your desk phone. meiti rings that device first and then connects you to the customer. Your choice is kept for the next calls.

Why it matters

You dial on the computer and talk on your phone or desk phone, without typing the number. Since only the call to the customer goes over the phone network, such a call costs the same as a call from the app.

How to use it

1. Tap "Call" in the ticket or on the contact and choose "Via phone number".
2. Tap "Choose a device or saved number" and pick your phone ("meiti app · …") or your desk phone ("Desk phone · …"). Offered are your phones with meiti calls active for this inbox and the desk phones assigned to you.
3. Your customer sees your meiti number. For another number: "Enter a number instead".

11 October 2026 Telephony

Windows: turn on calls on this computer right in "team & phone"

In the Windows app's "team & phone" window you can now switch on calling on this computer yourself: click your status under "Customer calls to you" → "Calls on this computer". It is the same switch as in your own member profile.

Why it matters

Anyone who wanted to call from the computer first had to go to the member profile. Now the switch sits where you make calls — next to "Audio devices …".

How to use it

1. On: you call customers and colleagues from the computer, and calls put through ring here.
2. Off: calls you place here go through your phone number.
3. If the computer is currently on for another organisation, meiti asks before moving it.

11 October 2026 Telephony

Announcement before the call: optional, in your own words

When meiti transcribes a call or records all of it, your customer has so far always heard "Verbindung wird mitgeschrieben." (or "aufgezeichnet") first. Now you decide per inbox: keep the announcement, replace it with your own sentence, or switch it off. Your own sentence applies on every path — calls from the app, via your phone number, from a desk phone and forwarded calls.

Why it matters

How you get your customers' consent is your decision: maybe you ask during the call yourself or already have it in writing. With the announcement off, the app also no longer asks for "Kunde ist einverstanden" when you start a transcript or recording during the call.

How to use it

1. Open "Settings" → "Setup & operations" → "Phone", section "Calls with people". Only admins can change it.
2. Switch "Announcement before the call" on or off.
3. Under "What your customer hears", enter your own sentence (300 characters at most). Left empty, your customer hears the automatic sentence as before, matching transcript and recording.

11 October 2026 API

Your own AI: sees when your team took over

When someone on your team takes over a conversation, replies, or switches auto-reply off or mutes it there, your own AI now learns about it too: message.received keeps arriving and carries autoReply (state: on|paused|off, pausedUntil). Your AI decides itself whether to answer. If it does, meiti delivers the answer and, the first time after the intervention, writes a note into the conversation.

Why it matters

Before, your AI heard nothing after a takeover. Now it can keep reading along, collect context or deliberately keep answering — and your team sees in the conversation when it does so although auto-reply is off.

How to use it

1. In your endpoint, check data.autoReply.state: anything but on means the team has the conversation.
2. To stay quiet, answer 204. To keep answering, send { text } as usual — skills and handover only run again once the conversation is back with the AI.

Example

{ "type": "message.received", "data": { "projectId": 67890, "autoReply": { "state": "off" } } }

More in the docs →

11 October 2026 Integrations

Zendesk connected directly: tickets and internal notes from every conversation

You can now connect Zendesk directly to meiti, without n8n. Callers become end users, enquiries go to the open ticket or get a new one, and every call and chat lands as an internal note with the summary on the ticket. Photos and documents from customers are attached.

Why it matters

Your support team works in Zendesk and starts every ticket with full context, without building and maintaining a workflow in between. The notes are internal: the customer gets no e-mail from them.

How to use it

1. Open "Settings" → "Setup & operations" → "Connected systems" → "CRM & industry software".
2. Under "CRM integration", choose Zendesk and enter your Zendesk address (e.g. firma.zendesk.com), the agent's e-mail and an API token. Create the token in the Zendesk Admin Center under Apps and integrations → APIs → Zendesk API.
3. Optional: tickets from meiti carry the tag "meiti". If Zendesk should not send them a receipt e-mail to the customer, exclude the tag in your trigger.
4. Good to know: Zendesk stops issuing new API tokens on 27 Oct 2026 and switches all of them off on 30 Apr 2027. For the time after that we are preparing the connection via the Zendesk sign-in.

More in the docs →

11 October 2026 Integrations

Pipedrive and HubSpot connected directly — and the webhook on top of your CRM

Besides HERO you can now connect Pipedrive and HubSpot directly to meiti. Callers become contacts, enquiries become deals (Pipedrive, HubSpot) or tickets (HubSpot with Service Hub), and every call and chat lands as a note on the deal or ticket. On top of any connected CRM you can also add a webhook, e.g. for n8n or Make.

Why it matters

Your team works in its CRM and sees there what was said on the phone and in the chat — no automation in between. If you still need your own workflows, you no longer have to choose between CRM and webhook: the customer and case numbers stay with the CRM, the webhook gets the same events as before.

How to use it

1. Open "Settings" → "Setup & operations" → "Connected systems" → "CRM & industry software".
2. Under "CRM integration", choose Pipedrive, "HubSpot (Deals)" or "HubSpot (Tickets)". Tickets need HubSpot Service Hub, deals work with every HubSpot plan.
3. Pipedrive: enter your personal API token (Pipedrive → Personal preferences → API). HubSpot: enter a Service Key (HubSpot → Settings → Integrations → Service Keys) with read and write access to contacts and deals or tickets, plus "files" for customer files.
4. "After every call and chat": "Contact + project" (default), "Contact only" or "Manual". Under "Pull from the CRM" you bring contacts and deals or tickets into meiti.
5. Webhook on top: in "Webhook in addition", tap "Add webhook" and enter the URL and optionally a bearer token.

More in the docs →

11 October 2026 Integrations

Your AI assistant guides you through the WhatsApp setup

The meiti MCP server has an area for account health and guided setup. For WhatsApp it explains the options with their pros and cons to Claude, ChatGPT and co., recommends the right one (shared inbox: your landline; personal inbox: your own WhatsApp Business App, synced only) and walks through Meta's onboarding step by step: business details, connecting WhatsApp, payment method, business verification.

Why it matters

WhatsApp setup is easy once someone sorts out the terms: WhatsApp, the WhatsApp Business App and Meta's business account are three different things. The assistant sees what your inbox has already done and always names exactly the next step.

How to use it

1. Connect your AI assistant to the meiti MCP server (see the MCP docs).
2. Say, for example: "Help me set up WhatsApp."

More in the docs →

10 October 2026 App

Start on the web: create your account, then two ways to go live

Under "Kostenlos starten" (/go) you create your account in the browser — with a mobile number or e-mail address and a code. Your inbox is there right away and you can try your assistant in the app. To reach the outside world — your own number, calls and messages — pick one of two ways: the free compliance call or a plan straight away.

Why it matters

You decide whether to talk to us first or get going right away. Nothing reaches the outside world until it is clear who the business is — that protects your number, your senders and your customers.

How to use it

1. Open "Kostenlos starten", enter your first and last name and a mobile number or e-mail address, "Konto anlegen", then confirm the code.
2. Free: "Compliance-Call buchen". After your compliance call we credit 10,000 credits once, and they don't expire.
3. Straight away: under "Sofort starten" pick Solo or Team and pay — your number, calls and messages are open right after.

More in the docs →

10 October 2026 App

Cleanup: delete recordings after a set time

"Clean up automatically" has a fourth rule: "Delete recordings". Voicemails and call recordings older than 30, 90, 180 or 365 days (or a number of your own) are deleted overnight. The message stays in the conversation — with the voicemail's text, the call's transcript and its summary — and shows "Recording deleted (cleanup)" instead of the player.

Why it matters

Recordings are the largest and most sensitive part of a conversation. With a time limit they are kept only as long as you actually need them — and what was said stays readable. Recordings already downloaded to a phone are removed by the app on its next sync.

How to use it

1. "Settings" → "Setup & operations" → "Clean up automatically" (owners and administrators only).
2. Switch on "Delete recordings", pick the time limit, check "Affected right now", save.
3. The other rules stay as they are: show enquiries as inactive, archive them and empty the archive — transcripts and summaries only go with the enquiry.

10 October 2026 Telephony

One phone system for every inbox

Your own phone system (SIP) is now connected once for the whole organisation instead of once per inbox. Every inbox has its own address on that connection – its phone number – which your phone system dials to reach it. Calls to an unknown address land in the default inbox.

Why it matters

Before, every inbox needed its own SIP account and desk phones belonged to exactly one of them: transfers into another inbox took detours, and switching SIP off in one inbox could delete phones another one still used. Now you set the phone system up once, every phone and extension serves every inbox, and extension numbers are unique within the organisation.

How to use it

1. "Settings" → "Setup & operations" → "Phone" → "Own phone system (SIP)": domain and credentials are the same for every inbox.
2. With several inboxes the section shows the "Address of this inbox" (sip:number@domain) – enter that address in your phone system as the destination for this inbox.
3. "Make this inbox the default" decides where calls without a matching address arrive.
4. The SIP switch only deletes the connection when no other inbox still has it on – otherwise the section is merely hidden.

10 October 2026 Telephony

Calls and forwards abroad — at the telephony provider's price

meiti now calls every destination our telephony provider has a rate for. Domestic calls cost the familiar rates. Abroad, a started minute costs the provider's connection charges, rounded up to whole credits, plus 3 (Solo), 2 (Team) or 1 (Enterprise) credits — never less than at home.

Why it matters

Customers, colleagues and on-call services aren't only in Germany. Instead of a fixed list of countries, the real price counts — so you can forward and call abroad too, and an expensive destination is never cheaper than it costs us.

How to use it

1. Calling: in the call sheet a line "International call · … credits/min" appears as soon as the number is abroad.
2. Forwarding: add destinations abroad under "Phones & numbers" as usual. meiti refuses special-rate numbers, destinations without a rate and very expensive destinations when you save them.
3. In the usage log, the part above the domestic rate shows as its own entry "International carrier charge".
4. If someone calls with a withheld number — or with a number from outside the EEA while the forward goes into the EEA — the person the call is put through to sees your inbox's number.

More in the docs →

10 October 2026 API

API: log mails from your own mailbox and notes

With POST /v1/messages/log your system files a message that was written outside meiti in a contact's project — a mail from your Gmail or Outlook mailbox, a WhatsApp from another tool, incoming or outgoing. meiti sends nothing and does not answer it. POST /v1/notes adds internal notes.

Why it matters

Your team and your assistant see the whole conversation, including what went through other channels: the assistant reads logged messages, incoming ones show as unread in the inbox. Notes stay with the team — they never reach the customer, and the assistant does not read them.

How to use it

1. API key: "Connected systems" → "API access".
2. Per message send direction (in/out), channel (email, whatsapp, sms, rcs) and text, for mails also subject and the Message-ID as externalId — the same id is filed only once.
3. Optional: ai: "pause" hands the project to your team, notify: true sends a push for incoming messages.

Example

{ "email": "erika.weber@example.com", "direction": "in", "channel": "email", "subject": "Angebot Badsanierung", "text": "Hallo, wann können Sie diese Woche vorbeikommen?", "externalId": "<CAF7x9Q@mail.gmail.com>" }

More in the docs →

10 October 2026 API

Your own AI: meiti's forward and alert as tools

An assistant with your own AI can now use forwarding and alert skills. Your AI triggers them itself by their key — in chat with executeSkills in its answer, on the phone with the skill frame, or via POST /v1/projects/{id}/skills/{key}. On the phone meiti really puts the call through; if nobody answers, the caller is back with your AI.

Why it matters

Your AI brings the logic, meiti the plumbing: putting calls through to team members, numbers and ring groups, SMS and WhatsApp alerts to the team. meiti keeps the hard rules — the skill's times, the skill limits per hour and call, your plan — so a mistake of your AI cannot overrun the team.

How to use it

1. "Settings" → "AI assistants" → your own-AI assistant → "Skills" → "Add skill": pick a forward or an alert.
2. Optionally set an announcement meiti tells the customer when the skill runs.
3. Copy the key and use it in your AI — message.received and session.started list the skills that may run right now.

Example

{ "text": "Ich verbinde Sie mit unserem Büro.", "executeSkills": ["buero"], "note": "Kunde wartet auf Rückruf zur Rechnung 4711" }

More in the docs →

10 October 2026 App

Who answers where — at a glance, schedules included

The "Who's answering right now" sheet (fox in the inbox, "Who answers where?" in AI assistants, "Who answers where right now?" on the profile page) is now a list instead of a diagram: per channel, who answers right now, which schedules exist — and right there "Switch" and "Add schedule". Every schedule has a pencil and a bin. The assistant cards show just one line naming the channels an assistant answers on.

Why it matters

Before, you had to tap a channel in the diagram to see whether a schedule was running, then "Switch assistant" to even reach the choice. Now everything is on one screen, and a change is: "Switch" → assistant → confirm.

How to use it

1. Inbox → fox icon, or "Settings" → "AI assistants" → "Who answers where?", or profile page → "Who answers where right now?" (the row already shows the answer as its subtitle).
2. On the channel: "Switch" (or "Assign" when nobody answers) → pick an assistant → confirm. "Add schedule" → pick an assistant → period or weekdays.
3. Tap the channel: there you can try it like a customer and open the channel settings.

9 October 2026 Telephony

Even when the AI fails, the request reaches your team

When the AI cannot route a request for technical reasons, the assistant no longer asks the customer to repeat themselves ("sorry, I couldn't process that"). It hands over instead: on the phone and in chat your fallback skill takes over; otherwise meiti notes the request for the team and asks only for whatever name and number are missing.

Why it matters

Before, a caller could hear "couldn't process that" twice, hang up, and leave you with no name or number. Now every request arrives with contact details. Nothing the customer already said is asked again, and a callback is only promised when someone was actually notified.

How to use it

1. Nothing to set up — this is on for every inbox.
2. Optional: "Settings" → "AI assistants" → pick an assistant → "When meiti needs help" → "When meiti can't place the request", and choose a fallback skill to handle these conversations.
3. Your team sees an "AI failure (…)" line with the reason in the conversation. The customer never sees or hears it.

9 October 2026 Integrations

HERO: every conversation in the logbook, appointments in sync, contacts and projects with one tap

After every call and every finished chat, meiti writes exactly one entry with the summary into the HERO logbook and links contact and project. Appointments travel between HERO and meiti in the direction you choose, and you pull contacts and projects from HERO with a button.

Why it matters

Your office works in HERO and no longer has to check meiti for what was said on the phone — it's on the project. Appointments planned in HERO get meiti's customer reminders, and appointments booked in meiti land in your HERO calendar. Existing customers and projects are in meiti from day one, so the assistant recognises them.

How to use it

1. Open "Settings" → "Setup & operations" → "Connected systems" → "CRM & industry software".
2. Under "CRM integration", choose Hero and enter the API key.
3. "After every call and chat": "Contact + project" (default), "Contact only" or "Manual".
4. "Appointments with Hero": "Off", "Hero → meiti", "meiti → Hero" or "Both ways". The default is "Both ways" — including for existing HERO inboxes.
5. Under "Pull from the CRM": "Pull contacts from Hero" and "Pull projects from Hero". You can repeat both any time; nothing in meiti is overwritten.

9 October 2026 Telephony

Every inbox puts calls through

The put-through switch is gone. When a handover has a phone target, the assistant now connects the caller in every inbox instead of only taking a callback note. "Put calls through" on a contact is now available in every inbox too.

Why it matters

Inboxes with only one number used to have transfers switched off automatically so calls wouldn't loop. Their callers heard "I can't put you through" even when someone was available. meiti now detects that loop itself — when targets are set up and during the call — so the switch is no longer needed.

How to use it

1. "Settings" → "AI assistants" → pick an assistant.
2. In "When meiti needs help" (in forward-all mode: "Forward to"), choose a person or number.
3. For individual customers: "Contacts" → open a contact → "Put calls through" → "Put calls through to …".

9 October 2026 Integrations

Appointment events on the CRM webhook — and CRM integrations plus the API on every plan

The CRM webhook now reports appointments too: created, confirmed, rescheduled, cancelled, finished and reminder sent, each with appointmentData. The CRM integration (webhook and Hero) is available on every plan with no monthly event limit, and the API (beta) is on for every inbox.

Why it matters

Your calendar or CRM learns right away when a customer confirms or cancels on their appointment page — so you can refill the slot. The previous limit of up to 100 webhook events a month is gone, so integrations no longer stop mid-month. You no longer have to switch the API on under "Features" first.

How to use it

1. Open "Settings" → "Setup & operations" → "Connected systems" → "CRM & industry software".
2. Under "CRM integration", choose "Webhook" and enter URL and token.
3. In your endpoint, handle the eventType values AppointmentCreated, AppointmentConfirmed, AppointmentRescheduled, AppointmentCancelled, AppointmentFinished and AppointmentReminderSent.
4. API key: "Connected systems" → "API access".

Example

{
  "eventType": "AppointmentConfirmed",
  "timestampUtc": "2026-10-14T16:02:11.512Z",
  "callbackUrl": "https://api.meiti.ai/api/webhook-callback/5f0c2e…",
  "contactData": { "meitiContactId": 18342, "phoneNumber": "+491701234567", "crmContactId": "K-1042" },
  "projectData": { "meitiProjectId": 67890, "crmProjectId": null, "projectName": "Heizungswartung" },
  "appointmentData": {
    "id": 5120, "externalId": "CAL-8812", "contactId": 18342, "projectId": 67890,
    "title": "Heizungswartung", "start": "2026-10-20T08:00:00", "startLocal": "2026-10-20T10:00:00",
    "durationMinutes": 60, "kind": "in_person", "status": "confirmed",
    "customerConfirmedAt": "2026-10-14T16:02:10.9910824", "rescheduledCount": 0
  }
}

More in the docs →

9 October 2026 Integrations

"Open in meiti" and "Call with meiti" straight from your CRM

With one link, your CRM, ERP or website opens the matching ticket in the meiti app — by meiti id, case number or customer number. A second link opens the call screen with a number. Also new is the developer guide with quickstart, recipes, reference and llms.txt for AI coding agents.

Why it matters

Whoever has a job open in the CRM jumps into the conversation with exactly that customer in one click — without searching or knowing which inbox it lives in. If the customer has no open ticket, meiti starts one. Nothing is dialled until you tap in the call screen.

How to use it

1. Keep the numbers: "Settings" → "Setup & operations" → "Connected systems" → "CRM & industry software" → switch on "Customer number" / "Case number". They arrive via the webhook answer or are entered in the app.
2. Add a link like https://m.meiti.ai/open/project?crmId=… or https://m.meiti.ai/open/dial?number=… in your CRM.
3. With several matches you choose under "Which ticket?". With none, the app says "Ticket not found".
4. For your IT: "Connected systems" → "API access" → "Developer guide & examples".

Example

<a href="https://m.meiti.ai/open/project?crmId=AZ-2024%2F117">In meiti öffnen</a>
<a href="https://m.meiti.ai/open/dial?number=%2B491701234567">Mit meiti anrufen</a>

More in the docs →

9 October 2026 API

CRM webhook: eventType is now sent as its name

The CRM webhook now sends eventType as text, as documented — for example "FinishedCall" instead of the number 1.

Why it matters

Integrations built against the docs didn't recognise events until now. If you checked against the number, you need to adapt — it's safest to accept both for a while.

How to use it

1. Read eventType as a string in your webhook endpoint.
2. Accept the legacy number for a while (0 = IncomingCallLookup … 5 = FormSubmitted).
3. Ignore unknown values — new ones are added, for example the appointment events.

Example

const name = typeof e === "number"
  ? ["IncomingCallLookup", "FinishedCall", "NewConversation", "ConversationPaused", "Manual", "FormSubmitted"][e]
  : e;

More in the docs →

8 October 2026 App

Contact list: see at a glance how to reach whom

Every contact now shows as a uniform card: name, contact type, contact person (else address or number), customer number, the contact's channels and one status — "Blocked", "Personal" or where their calls are put through.

Why it matters

You see in the list whether a customer is reachable on WhatsApp, what their customer number is and whether their calls currently ring straight through to a colleague — without opening each contact. Every card is the same height, so the list scrolls smoothly.

How to use it

1. Open the "Contacts" tab; search results use the same card.
2. The customer number appears once one is stored on the contact.
3. Set a call route on the contact under "Put calls through".

7 October 2026 API

API: choose channel, sender and WhatsApp template yourself

POST /v1/messages now takes a priority list channels (channels, sender ids or default), respects the contact's settings via respectContactSettings, and sends an approved template via whatsApp when the 24-hour window is closed. New endpoints: GET /v1/senders and GET /v1/whatsapp/templates.

Why it matters

Your software decides whether an invoice notice goes by WhatsApp first and otherwise by SMS, or from exactly which mailbox. Important service messages arrive even if the customer hasn't written for days, because the template goes out instead of the text. Marketing without consent is always blocked.

How to use it

1. API key: "Settings" → "Setup & operations" → "Connected systems" → "API access".
2. List sender ids with GET /v1/senders and templates with their variable count with GET /v1/whatsapp/templates.
3. Pass channels and optionally whatsApp in POST /v1/messages. The response carries channel, senderId, sentAsTemplate, waitingForReply and consentOverridden.

Example

curl https://api.meiti.ai/v1/senders -H "X-Api-Key: $MEITI_API_KEY"

# "rechnung_fertig" is a placeholder: use a name from GET /v1/whatsapp/templates
curl https://api.meiti.ai/v1/messages \
  -H "X-Api-Key: $MEITI_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: invoice-2024-117-ready" \
  -d '{
    "phone": "+491701234567",
    "text": "Hallo Frau Weber, Ihre Rechnung 2024-117 ist fertig.",
    "purpose": "service",
    "channels": ["whatsapp", "sms"],
    "whatsApp": { "template": "rechnung_fertig", "language": "de", "variables": ["Frau Weber", "2024-117"] }
  }'

More in the docs →