Krisp
Order details in the chat - confirmed by your own server
A customer pastes an order number and asks for its details. Krisp asks for the email the order was placed with, checks both with your own server over a signed request, and posts what your server returns - a login, a licence key, a download link - in the chat. Your orders never live in Krisp, and a person takes over whenever a lookup cannot finish.
How signed order lookup works in the chat
The customer types an order number
Krisp spots it with the pattern you set -
ORD-12345by default, or presets for Shopify’s#100234, WooCommerce, grouped keys and UUIDs - and offers “Get my credentials” or “Talk to an agent”. The website chat shows buttons; on WhatsApp, Instagram, Messenger, Telegram and email the customer replies “credentials” or “agent”. A customer who only says “I purchased yesterday” is asked for the order ID first.Your server is asked
Once the customer types the email the order was placed with, a small endpoint on your side receives the order ID, that email and the channel the answer would go to, signed with a secret only you and Krisp hold and timestamped against replays. It answers with the details, “not ready yet”, or that no such order matches that email.
The details, or a person
The details are posted in the chat under your assistant’s name. A wrong email uses up one of the tries you allow; too many tries, a request for a person, or an endpoint that does not answer hands the thread to a teammate, with what happened in the thread.
Built to keep customer order data private
Signed, every time
Each request carries an HMAC-SHA256 signature over its timestamp and body. Your endpoint checks both and answers nothing to anyone else. The secret is stored encrypted; an owner or admin can show it again, copy it and rotate it, and a test request from the dashboard shows what your endpoint answers - credential values masked - before you switch the lookup on.
Public addresses only
The endpoint must be reachable on the public internet over HTTPS. Its name is resolved again at every call and the request goes only to the public addresses that were checked: a private or local address is refused, redirects are not followed, and an answer is capped at 64 KB, so Krisp can never be pointed at something on your network it should not see.
Yours to shape
The order-number pattern, tried live on a sample message and timed on long ones before it is saved, then run under a time limit on every message; how many tries a customer gets; and the name the assistant answers under. The request names the channel, so your server can refuse to release details on one. The lookup has a switch of its own: it answers with the AI chatbot on or off, and stays out of a conversation your team is handling. Switch it off at any time; the chat goes on without it.
Related order lookup features
Stop answering “where is my order?” by hand
A small endpoint on your side, and the chat does the rest.