Automation · Customer service and scheduling
Answer on WhatsApp your event dates and the status of a Ticket Tailor ticket purchase
An AI agent answers on WhatsApp which events and dates are coming and tells the buyer which order and tickets they have in Ticket Tailor.
How do I answer on WhatsApp the dates of my events and the people who say their Ticket Tailor tickets never arrived?
A Met connected to Ticket Tailor lists your events or the dates of a series and answers with what is published, not with a list someone copied. If the person asks about an event, it opens its details. If they say they bought and their tickets never arrived, the Met finds their order by name or email, opens it and reviews the issued tickets to tell them what is on record. It does not charge, issue or void tickets in this procedure: if the order does not show up, it tells the person someone on the team will check.
What starts it
When the customer writes
It starts when someone writes on WhatsApp asking about an event, its dates or a purchase they already made. There is no trigger to configure: the Met assigned to the line runs the procedure inside that conversation.
Nothing to set up. The Met assigned to that channel picks up the conversation and runs the procedure inside it.
Who runs it
Events support Met
Customer service team
This is not a named, seeded Met. It is the Met that answers the organizer's WhatsApp, with Ticket Tailor connected. Its work ends when the person knows which dates there are or which order and tickets they have on record.
Run by the customer support Met
Channels: WhatsApp
What you need connected
- Ticket Tailor Sell and serve
5 steps · 6 tools
The procedure, step by step
Each step shows the tool that runs. They belong to the real connector: if one of them stopped existing, this page would not build.
- 1
List the published events
The Met lists the events in your Ticket Tailor account and answers with the upcoming ones. Since it checks on every question, a new event shows up in the answer without touching the Met.
- 2
Show a series' dates
If the event repeats, the Met lists the dates of that series to say which days are left. That way it does not mix up two showings of the same event.
- 3
Open the event details
When the person picks an event, the Met opens its details and answers with what Ticket Tailor returns. To buy, it shares the link your team left in the skill.
- 4
Find the buyer's order
If the person says they already bought, the Met lists the orders, finds theirs by the name or email they give and opens it to see what they bought and for which event.
- 5
Review the issued tickets
The Met reviews the issued tickets for that order and tells the person how many they have and for which date. If nothing shows up, it does not invent a ticket: it says someone on the team will check.
Before you start
What you need ready
The Met solves none of these for you. If one is missing, the automation stops there.
-
Events published in Ticket Tailor
Your team has its events and dates in Ticket Tailor. Whatever is not published there, the Met cannot answer.
-
Ticket Tailor connected
In Met, open Connections → Ticket Tailor → Connect and authorize the account. This procedure only needs the read actions for events, orders and tickets.
-
A WhatsApp line with the Met assigned
The organizer connects its WhatsApp Business API line and assigns the Met that serves the public. The conversation happens there; Ticket Tailor remains the source of data.
The limits
What this automation does NOT solve
Better said here than discovered halfway through the rollout.
-
It does not charge for or sell tickets inside the chat. The purchase happens on the Ticket Tailor page, through the link the Met shares.
-
It does not resend tickets to the buyer's email. It can tell them which tickets were issued, but your team does the resending in Ticket Tailor.
-
It does not void or change tickets. Voiding exists in the connector, starts switched off and this procedure does not use it.
-
It does not find an order if the person gives no detail that appears in it. Without the purchase name or email, the Met has nothing to search with.
FAQ
Questions about this automation
The Met answers with it from the next question, because it lists the events every time. There is no copy stored in Meteor that goes stale.
Only if the event details in Ticket Tailor include that figure. If they do not, the Met does not calculate or guess it.
The connector has the hold action, but this procedure does not use it. It arrives switched on: if you want it, the skill says when to use it; if not, the admin turns it off in Connections.
Keep going
Other automations built on the same tools
Customer service and scheduling
Open a Linear issue from a customer report on WhatsApp and tell them how it is going
How do I make customer reports on WhatsApp arrive in Linear as issues?
Customer service
- Starts:
- when the customer writes
- Steps:
- 5, with 6 real tools
- Needs:
- Linear
Customer service and scheduling
Open a Freshdesk ticket from WhatsApp and tell where it stands
How do I turn a complaint that arrives on WhatsApp into a Freshdesk ticket without copying it by hand?
Customer service
- Starts:
- when the customer writes
- Steps:
- 5, with 10 real tools
- Needs:
- Freshdesk
Customer service and scheduling
Open a Gorgias ticket from WhatsApp and escalate it to the team that solves it
How do I move a complaint that arrives on WhatsApp into Gorgias without copying it by hand or losing what the customer said?
Customer service
- Starts:
- when the customer writes
- Steps:
- 5, with 7 real tools
- Needs:
- Gorgias
Customer service and scheduling
Open a Jira issue from a report that comes in on WhatsApp and answer how it is going
How do I make customer reports on WhatsApp arrive in Jira as issues?
Customer service
- Starts:
- when the customer writes
- Steps:
- 5, with 6 real tools
- Needs:
- Jira y Confluence
Want this automation running on your own data?
We will show it to you with your accounts connected, not with a canned demo.