EzyConn tells the right person when it matters: a new message, a customer handed over, a booking made. Alerts reach your team in the inbox, on the desktop and in Slack, and your customer gets the confirmation that matters to them.
New message from Lena FischerDo you deliver to Galway?
09:14
Sam says yes to a person on WhatsApp
Priya’s inbox
Sam Patel has been connected to you via AI escalationOrder arrived damaged, wants a replacement.
09:14
The same hand-over, posted for the team
Slack, #z-lc-sam-patel-0932
New escalation from Sam PatelRouting Reason: Visitor is requesting to speak with a live agent.
09:31
Ana books a cut and colour in the chat
Ana’s inbox
Booking Confirmed: Cut and colourThursday 8 October, 15:00.
A worked example of one morning. A website chat message raises a desktop alert. A WhatsApp customer who says yes to a person is assigned to a teammate, who is told in the inbox, and the hand-over is posted to Slack with its routing reason. A customer who books in the chat receives a confirmation email.
Worked exampleThe people and times are invented. The alert wording is EzyConn’s own.
Who hears what
Your team hears what needs them.Your customer hears what matters.
Two audiences, each told about the moments that change what they do next.
Your team
A new message arrives
A sound and a toast in the inbox that opens the conversation. A desktop alert too, if the tab is in the background.
Inbox and desktop
A customer is handed to them
When a customer says yes to a person, a teammate is assigned and told straight away, with the conversation attached.
Inbox and Slack
A booking is made
Your team hears about each new appointment, so nobody finds it in the diary by surprise.
Email and in the app
A process needs telling someone
Any process can include a step that tells someone what happened, from Starter.
Inside a workflow
Your customer
Their booking is confirmed
An email with the subject “Booking Confirmed” and the service name, queued the moment the appointment is written.
Email
A person is on the way
When they accept a person, the chat says so: “Thanks, I’m connecting you to a support specialist now. Please hold for a moment.”
In the conversation
Nobody is free right now
If every teammate is busy, the chat tells them that honestly rather than leaving them waiting in silence.
In the conversation
In Slack
Every new chat and hand-over,posted where your team already is
Each conversation gets its own channel, with the question, who is asking and where from. Join the channel, reply, and the customer reads it where they wrote.
Live ChatApp
New chat from Lena Fischer. To respond, join #z-lc-lena-fischer-4821. @here
Visitor Question
Do you deliver to Galway on a Saturday?
Reply in Channel
#z-lc-lena-fischer-4821
Visitor Information
Name
Lena Fischer
Location
Galway, Ireland
Email
lena@example.com
Browser
Chrome on Windows
Page
example.com/delivery
Live ChatApp
New escalation from Sam Patel. To respond, join #z-lc-sam-patel-0932. @here
Visitor Question
Routing Reason: Visitor is requesting to speak with a live agent. Please review the chat history and respond promptly.
Sam Patel (9:13 AM): My order arrived damaged. Can someone sort a replacement?
Ivy (9:13 AM): I’m sorry about that. A replacement needs someone from the team. Would you like me to bring a person in?
Sam Patel (9:14 AM): Yes please
Reply in Channel
#z-lc-sam-patel-0932
Visitor Information
Name
Sam Patel
Phone
+44 7700 900318
Browser
WhatsApp
A channel per conversation, or a thread
Give every conversation its own channel, as here, or keep them as threads in one channel you pick.
As much detail as you want
Minimal, standard or detailed: from just the question to the full visitor information shown here.
Hand-overs arrive with the history
An escalation says why it was raised and carries the conversation so far, so nobody asks the customer to repeat themselves.
Whichever channel they wrote on
Website chat, WhatsApp and texts to your Twilio number all arrive the same way, labelled with where they came from.
Worked exampleThe visitors are invented. The layout and wording are the Slack post’s own.
Quiet by design
Loud when it matters,quiet when it does not
A team alerted about everything stops reading any of it. These rules keep the useful alerts useful.
Not about what you are reading
No toast for the conversation already open in front of you. Being interrupted about the thing you are reading teaches people to ignore alerts.
Desktop alerts only when you are away
The browser alert fires when the tab is in the background, and only if you switched it on.
Off means off
Switch an alert off and it stays off. The setting is read every time, not remembered from this morning.
Urgent stands out
Mark a conversation urgent, or notify a supervisor from inside it, when the routine flow is not enough.
NotificationsWhat we email you, and how this browser tells you a message has arrived.
Email
Security alertsA new sign-in, a password change, or two-factor turned on or off.
Team activitySomeone joins your account, or an invitation is accepted.
Product updatesWhat changed in EzyConn, a few times a year.
Offers and tipsOff unless you ask for them.
This browser
Desktop notificationsWhen a message arrives and this tab is in the background.
Drawn from the profile pageThe switches and their wording are the portal’s own.
Plans
Team alerts are on every plan.Texts are billed by Twilio.
Inbox, desktop and email alerts for your teamOn every plan
Posting to Slack, and replying from itOn every plan
Booking confirmation emails to customersFrom Starter
When a customer says yes to a person, a teammate is assigned and notified in the inbox, and if Slack is connected the conversation is posted to the channel you chose. A new message also plays a sound and shows a toast, and raises a desktop alert when the tab is in the background.
Can alerts go to Slack?
Yes. Pick the channel to post in, choose one thread per conversation or a separate channel per conversation, and set how much detail is posted: minimal, standard or detailed. Replies typed there reach the customer.
Does the customer get a booking confirmation?
Yes, by email, with the subject “Booking Confirmed” and the service name. It is queued as soon as the appointment is written.
Can I turn desktop alerts off?
Yes. Desktop alerts are a switch on your own profile, and they only appear when the EzyConn tab is in the background. Switching them off is respected every time.
Which emails does EzyConn send me?
Security alerts, team activity and product updates, each with its own switch. Offers and tips stay off unless you ask for them.
Which plan do I need?
Inbox, desktop, email and Slack alerts are on every plan. A booking confirmation comes with booking in the chat, from Starter, and a notify step inside a process comes with workflows, from Starter. Text messages are billed by Twilio.