POST /v1/events, the steps in ContactShip and what to measure. The data in the examples is made up.
Restaurants and delivery
Who it is for. Food chains that take orders with an AI agent on WhatsApp or by phone. The problem. You have thousands of conversations a week, but the order is closed in your POS or your ordering platform. You don’t know who stopped ordering, or how much the agent that answers the phone sells. What your system sends. Each order, when it is closed in the POS:Win back the ones who stopped ordering
purchase Did it + purchase Did not do it in the last 60 days, and click Select the N that match.Make the most of big days
purchase Did it at least 3 times in the last 90 days.Measure what came back
store, channel and coupon are at the top level of params, a custom report also shows which store and channel people buy through, and how many used the campaign’s coupon.
Phone sales with AI
Who it is for. Brands that sell monthly-use products by phone —supplements, cosmetics, pet food— to people who leave their details on an ad, often with cash on delivery. The problem. Your system calls the lead with an AI agent as soon as it arrives, and the agent closes the sale. But a closed sale is not a paid sale: some orders are refused at the door. You don’t know which agent brings sales that get delivered, and you don’t call in time for the second purchase. What your system sends. The lead, the order and what happens with the delivery:Keep calling as you do today
Measure which agent really sells
order_delivered, Total amount, split by Credited AI agent, with a 14-day window. Another one just like it with order_returned tells you which agent brings the most refusals.Follow up with the ones who did not buy
generate_lead Did it in the last 3 days + purchase Did not do it in the last 3 days.Be on time for the repeat purchase
order_delivered Did it in the last 30 days + order_delivered Did not do it in the last 20 days + purchase Did not do it in the last 20 days. They received it between 20 and 30 days ago and have not ordered again. Send them a WhatsApp message and follow the result with Repeat purchases.Collections
Who it is for. Lenders, credit unions, schools and any business that charges in installments. The problem. Your system already launches AI calls based on each installment’s status: before it is due, right after it is due and when it is late. The payment comes in through the bank or the payment gateway, and you don’t know how much each call collected, or how much would have been paid anyway. What your system sends. When an installment becomes overdue and when a payment comes in:Name the events
loan_number and installment to Highlighted data. Your team sees on the contact’s record which installment each customer owes and which one they paid.Keep calling as you do today
Measure what each agent collects
payment_received, Total amount, split by Credited campaign or agent, with a 7-day window. Not credited is what was paid with no AI call or campaign in those 7 days.Remind the ones who still have not paid on WhatsApp
payment_overdue Did it in the last 15 days + payment_received Did not do it in the last 15 days.Clinics and medical practices
Who it is for. Clinics, labs and medical centers that serve patients on WhatsApp, Instagram or Messenger and confirm appointments with an AI agent. The problem. Many prospects come in from ads and social media and never book, and some patients miss their appointment and never book again. The appointment lives in your scheduling system. What your system sends. The prospect, the appointment and what happened with it:Win back the ones who did not book
generate_lead Did it in the last 7 days + appointment_booked Did not do it in the last 7 days. Replies land in the inbox, where your AI agent or your team handles them.Rebook no-shows the same day
Measure how many appointments each action brings
appointment_booked, Distinct contacts, split by Credited campaign or agent, with a 7-day window. Since specialty is at the top level of params, you can also split it by specialty.Add up the revenue
appointment_attended and its amount, Total amount split by specialty tells you how much each specialty bills.Schools and courses
Who it is for. Language schools, business schools and course platforms that qualify prospects on WhatsApp and hand the best ones to an advisor. The problem. Your AI agent qualifies each prospect and hands them to an advisor, but the enrollment is paid in your school system. You don’t know how many prospects end up enrolled, or who to offer the next course to. What your system sends. The prospect, the trial class, the enrollment and the end of the course:See each student's journey
Follow up with the ones who tried and did not enroll
trial_class_attended Did it in the last 14 days + enrollment Did not do it in the last 14 days.Offer the next course
course_completed Did it in the last 30 days + enrollment Did not do it in the last 30 days, send them a campaign or have your system call them with an AI agent.Measure enrollments
enrollment, Distinct contacts and Total amount, split by Credited campaign or agent, with a 14-day window.purchase; if you want to use them for enrollments, send them with that name.Technical support
Who it is for. Manufacturers and tech companies with a help desk: an AI agent answers and routes, and your team solves. The problem. When an installer or a customer calls, your team doesn’t know which devices they registered, whether they are under warranty or whether they already have an open repair. All of that is in your ERP. What your system sends. The devices each customer registers and their repairs:Give your team context
model and rma_number to Highlighted data. Your team sees it in the inbox contact panel and on the contact’s record, without opening another system.Find your best installers
product_registered Did it at least 10 times in the last 90 days. They are the ones who install the most: invite them to a training or to your partner program with a WhatsApp campaign.Tips for any case
- Send the phone in international format. It is what ties the event to the contact’s conversations and calls.
- Use
event_idwith the order, installment or appointment number. If you retry, nothing is duplicated. - Put at the top level of
paramswhatever you want to split reports by, such as the store, the product or the specialty. What goes insideitemscannot be used in reports. - Send the sale with its real time in
occurred_at. Crediting compares it with campaigns and calls, and a call counts from when it begins. - Crediting counts campaigns and answered calls with AI agents. Conversations the customer starts, calls nobody answered and calls handled only by people do not count.
- Do not send sensitive data in
params: no diagnoses, card numbers or passwords. - Campaigns are built by hand, for example once a day or once a week. Sending them automatically when an event arrives does not exist yet. To react right away, have your system launch the call through the API.
