Skip to main content

Delivery platforms: Rappi, DiDi Food and Uber Eats

Orders and customer messages from the three platforms reach the omnichannel inbox, the AI agent answers "where is my order", and the restaurant calls the customer from the order.

Install​

Open Admin > Settings > Integrations > Integrations, choose Rappi, DiDi Food or Uber Eats and paste the partner client ID and client secret (sealed with the company key). Then create an inbound hook endpoint for the connector and give the platform its address POST /hooks/int/<connector>/<install_key>; the connector keys are rappi, didi_food and uber_eats. The default signature check is hmac_sha256 over the body with the client secret, in the header Rappi-Signature, X-Didi-Signature or X-Uber-Signature.

Each platform gives partner API access on request (Rappi restaurants integrations API for Mexico, DiDi Food open platform, Uber Eats Marketplace API with the scopes eats.order and eats.store). Ask for sandbox credentials first.

What arrives​

PlatformEvents used
RappiNEW_ORDER, ORDER_STATE_CHANGED, ORDER_EVENT_CANCEL, CUSTOMER_MESSAGE
DiDi FoodorderNew, orderStatus, orderChat
Uber Eatsorders.notification (the order is fetched), orders.cancel, orders.status_changed

One order is one inbox thread: the first post lists the items, the total and the customer's note; state changes and customer messages follow. A redelivered webhook is stored once. The customer's address is never copied.

AI agent​

  • order_status finds an order by code or id, or by the caller's phone among the orders in progress, and answers in the caller's language. The answer never contains the customer's name, phone or address.
  • customer_call_check tells whether the restaurant can call now. It never returns the number.

Call the customer from the order​

Open the order's conversation in the inbox (console or MonoPhone) and choose Call customer. Your own phone rings first; when you answer, the PBX dials the customer with your own line, outbound rules and calling permissions.

The platform's masked number is the only number used when one exists, so the customer's real number is never shown. When the masked line asks for a PIN, the inbox shows it next to the call: key it in when the line asks. The call is refused, with a clear message, when the order has no number, after the mask expires, or once the order is over. Who may call follows who may answer the conversation (the department of the delivery channel).