Alex by Adelante · AI forward deployed engineer
Fix your AI support agent from Slack.
Alex is Adelante's AI forward deployed engineer for teams running an AI support agent. When the bot gets something wrong, tell Alex like you'd tell a teammate. It works out why and fixes it, then shows you the fix working.
Lives in Slack, WhatsApp or iMessage, wherever your team already talks.
Included with Adelante's managed service. Also available on its own if you already run your own AI support agent.
What Alex does
The stuff that used to wait for an engineer.
01 / 06
“Why did the bot say that?”
Send Alex the ticket or a screenshot. It reads the whole conversation, checks what the bot looked up and tells you what actually went wrong.
#cx-opsSlack DanaHead of CX14:02
@Alex why did the bot offer a refund on #20874? that one was already refunded
AlexAI14:04
Found it: The refund lookup came back 'refund pending' and the agent read that as no refund, so it offered a new one. The real refund went out Sep 24 and is still settling.
Looked at
Tool call record · refund lookup
- Order
- #20874
- Status returned
- refund pending
- Agent read it as
- Not refunded
- Refund issued
- Sep 24, settling
AlexAI14:05
Same mistake in 6 other conversations since Sep 24. I can have it treat 'refund pending' as refunded and tell the customer when the money lands. Want me to?
02 / 06
“We changed the returns policy.”
Tell Alex what changed. It finds every place the old policy is written down and updates all of them, so the bot stops quoting the old one.
Northline CX teamWhatsApp NoaSupport lead16:02
@Alex bot told a customer holiday returns are 30 days. this year it's 60 for orders placed Nov 1 to Dec 24. can you update?
AlexAI16:04
The 30-day window is written in two places, the 'Returns and exchanges' article and rule 7 of the instructions. One question: Do the 60 days count from delivery or from the order date?
NoaSupport lead16:09
from delivery
AlexAI16:12
Both updated with the holiday exception, and I read them back to be sure. Nothing else in the article or the rules changed.
Changed
Holiday exception added in two places
Returns and exchanges, paragraph 2
Added: Orders placed Nov 1 to Dec 24 can be returned within 60 days of delivery.
Agent instructions, rule 7
Added: For orders placed Nov 1 to Dec 24, accept returns within 60 days of delivery.
03 / 06
“The order lookup is broken.”
Alex follows the problem into the integration and fixes it there, even when that means changing code. Then it reruns the case that failed.
Northline support leadsiMessage OmerFounder08:41
@Alex a retail customer asked about order 5120 and the bot quoted them a wholesale order with the same number. can't happen again
AlexAI08:44
The lookup hits both stores and takes whichever answers first. This time wholesale won. Your agent only talks to retail customers, so I'd limit the lookup to the retail store. OK?
OmerFounder08:45
yes. retail only
AlexAI08:58
Retail store only now. Order 5120 comes back with the retail order, and there's a new automatic check for numbers that exist in both stores.
Changed
Order lookup updated
Removed: Searches wholesale and retail, returns the first match
Added: Searches the retail store only
Added: New automatic check for numbers in both stores
04 / 06
“Why are handoffs up this week?”
Alex reads the conversations and tells you what's driving it, with the numbers. There's usually one fix that matters most, and it tells you which.
#cx-opsSlack DanaHead of CX08:30
@Alex handoffs looked way up last week. what happened?
AlexAI08:52
Up from 61 to 97. I read all 97. 41 of them were questions about the Ridge 40 carry-on, which launched Sep 22 and isn't in the agent's knowledge at all.
Found
Handoff reasons, Sep 21 to Sep 27
97 conversations the agent handed to a human, out of 1,205 it handled
- Ridge 40 questions, no knowledge entry
- 41
- Address change after shipping, by rule
- 22
- Asked for a human first
- 14
- 9 other reasons
- 20, none above 4
AlexAI08:53
I'd add a Ridge 40 knowledge entry with the dimensions and weight and a clear carry-on answer. 17 of the 41 asked about European cabin allowances and the product page doesn't cover that. What's the answer?
05 / 06
“Hold that until legal signs off.”
Alex keeps track of what's pending. When legal says yes two days later, it picks the change back up without anyone explaining it again.
Northline CX teamWhatsApp NoaSupport leadTue 11:20
@Alex we want the bot to stop offering the extended warranty on refurbished items. legal is still on the wording so hold for now
AlexAITue 11:21
Noted, holding until legal signs off. When they do, I'll pull the extended-warranty offer from rule 9 and the 'Refurbished items' article. Nothing moves before then.
NoaSupport leadThu 09:05
@Alex legal approved. use this line: 'Refurbished items carry the standard one-year warranty.' go
AlexAIThu 09:11
Rule 9 and the 'Refurbished items' article both say 'Refurbished items carry the standard one-year warranty' now. The extended-warranty offer is gone from both. I read them back to confirm.
Changed
Extended-warranty offer replaced
Rule 9 and the 'Refurbished items' article
Removed: Offer the extended warranty on refurbished items.
Added: Refurbished items carry the standard one-year warranty.
06 / 06
“Check next week if the fix held.”
Alex schedules the check, runs it once and posts the result in your channel, with the before and after.
#cx-opsSlack DanaHead of CXSep 29 09:52
@Alex can you check in a week that the EU fix held?
AlexAISep 29 09:52
Sure. Tuesday Oct 6 at 09:00, posted here in #cx-ops. I'll compare EU- lookups since the fix against the 23 failures before it. One run, it won't repeat.
AlexAIOct 6 09:00
The EU fix held. Sep 29 to Oct 5, 34 of 34 EU- lookups found an order. Before the fix it was 0 of 23. Nothing else is scheduled.
Found
EU fix check, Sep 29 to Oct 5
EU- prefixed order lookups run by your support agent since the fix
- Lookups run
- 34
- Found an order
- 34 of 34
- Before the fix
- 0 of 23
- Handed off as 'order not found'
- 0, was 17 of 19
Where Alex works
It lives in your team chat and works on your agent.
01 / 03
In Slack, WhatsApp or iMessage
Add Alex to the channel or group you already use. Anyone there can ask it things, and it follows the conversation, so you don't have to repeat yourself.
Northline CX teamWhatsApp OmerFounder10:12
Berlin pop-up confirmed: Oct 16 to 19 at Alexanderplatz, 10:00 to 20:00. returns from the pop-up go through the online store
NoaSupport lead10:15
@Alex can the bot answer questions about this?
AlexAI10:16
Right now it can't. There's no entry for the Berlin pop-up, so it'd tell customers Northline only sells online. I can add the dates, address, hours and the returns line from Omer's message above. Want me to?
Looked at
Picked up from this group
- Dates
- Oct 16 to 19
- Place and hours
- Alexanderplatz, 10:00 to 20:00
- Returns
- Through the online store
- Source
- Omer's message at 10:12
02 / 03
Inside every ticket
Ask about any ticket and Alex shows you the whole story in one reply. You see what the customer said, what the bot looked up and which rule it followed.
#cx-opsSlack DanaHead of CX13:05
@Alex pull everything on #21390. customer emailed Omer saying the bot 'gave up on her'
AlexAI13:07
She asked to change her delivery address on Sep 26. The order had already shipped, so rule 12 handed her to a human. Problem is the handoff note didn't include the new address she'd just given.
Looked at
Full record · #21390
- Transcript
- 7 messages, Sep 26, 14:02 to 14:11
- Tool calls
- Order lookup, 1 match, shipped Sep 25
- Integration diagnostics
- 2 calls, no errors
- Rule applied
- Rule 12, no address change after shipping
AlexAI13:08
Your team then asked her for the address a second time, and she dropped off. Want me to put the new address in the handoff note going forward?
03 / 03
Inside the agent itself
Alex can change what the bot knows, the rules it follows, its tool settings and the integrations Adelante built for you. It posts every change in your channel with who asked for it.
Northline support leadsiMessage OmerFounderFri 17:05
@Alex what did you change this week?
AlexAIFri 17:06
Four changes this week, all requested by your team. Two to the agent's text and two to integrations, and nothing else.
Looked at
Changes, Sep 28 to Oct 2
- Mon · Knowledge
- Holiday returns, 30 to 60 days. Asked by Noa
- Tue · Integration
- EU orders routed to the EU store. Asked by Dana
- Wed · Instructions
- Cinder added to the final-sale list. Asked by Noa
- Thu · Integration
- Order lookup limited to retail. Asked by Omer
AlexAIFri 17:07
Want this every Friday? Say the word and I'll post it here weekly.
How it works
The questions CX leads ask us first.
01 / 04
“Can it see other companies' data?”
No. Every customer gets their own Alex, with its own memory and access. Yours only knows your agent and your setup.
Northline support leadsiMessage OmerFounder17:20
@Alex friends of ours at another brand are on Adelante too. can you check how their bot handles pre-order questions?
AlexAI17:21
Can't do that one. I only work on Northline's agent and I can't see any other customer's workspace or conversations. Happy to show you how your own agent handles pre-order questions though.
Looked at
Alex's workspace · Northline
- Workspace
- Northline only
- Memory
- Northline's decisions and open work
- Credentials
- Northline's agent and integrations
- Other customers
- No access
OmerFounder17:23
fair. do that
AlexAI17:31
Last 30 days: 84 pre-order questions, 71 resolved by the agent. All 13 handoffs were people asking for a ship date it doesn't have. Want me to add ship dates?
02 / 04
“Will it change things on its own?”
No. Alex tells you what it wants to change and waits. Nothing goes live until someone on your team says yes.
#cx-opsSlack NoaSupport lead11:02
@Alex bot offered a return label for a final-sale item on #21044. we don't take returns on final sale
AlexAI11:04
Rule 4 lists final-sale items by name and the new Cinder collection isn't on it yet. I can add it and have the agent point to the final-sale terms instead of offering a label. Ship it?
NoaSupport lead11:10
ship it
AlexAI11:14
Cinder's on the rule 4 list now, and the agent cites the final-sale terms instead of offering a label. Read the rule back, the other exclusions are untouched.
Changed
Rule 4, final-sale exclusions
Rule 4, final-sale items (no returns)
Added: Cinder collection, all items
Added: If a customer asks to return a final-sale item, explain the final-sale terms and offer no label.
03 / 04
“How do I know the fix worked?”
Alex reruns the ticket that failed and shows you the result. If something is still open, it says so in the same message.
Northline CX teamWhatsApp NoaSupport lead17:40
@Alex bot promised next-day delivery on a Friday 5pm order. cutoff is 2pm and we don't ship weekends. fix it and show me it's fixed
AlexAI17:49
The delivery rule had the 2pm cutoff but nothing about weekends. I added 'no dispatch Saturday or Sunday' and reran the Friday 5pm order. It quotes Tuesday now.
Checked
Verification
- Done: Weekend rule added to the delivery rule and read back
- Done: Friday 5pm order rerun, and the agent quotes Tuesday
- Done: Monday 1pm order rerun, and it still quotes next day
- Blocked: Public holidays aren't in the rule yet and need your list
AlexAI17:50
One gap: Public holidays aren't in the rule yet. Send me your list and I'll add them.
04 / 04
“What if it can't fix something?”
Then it goes to Adelante's engineers, with the error and everything Alex already found. You don't have to chase anyone.
#cx-opsSlack DanaHead of CX10:02
@Alex fyi the billing screen in the Adelante dashboard errors out when I open August's invoice
AlexAI10:05
That screen's outside my reach, but I can see the August invoice request failing with 'invoice not found'. Sent it to Adelante's engineers with the request ID. They'll reply in this thread.
Looked at
Handed to Adelante engineering
- Screen
- Billing, invoices
- Error
- Invoice not found, August
- Request ID
- 8f3a-21c6
- Sent with
- This thread and the diagnostics
TamirAdelante15:40
August invoice was sitting under your old billing account. moved it, the screen opens now. thanks for the request ID Alex, saved me a hunt :)
Get Alex
Two ways to get Alex.
Standalone
Alex for the agent you already run
If you already run your own AI support agent, Alex joins your team chat and takes the 'why did the bot do that' work off your engineers. On the demo we check what it can reach in your setup.
Included with Adelante
Alex inside the managed service
Adelante builds and runs your AI support agent, and Alex is how your team asks for changes. You tell it what needs to change, and we take care of the rest.
If you're already with Adelante, Alex is included. Tamir switches it on and adds it to your channel.
Alex FAQ
What teams ask before they let Alex in.
What is an AI forward deployed engineer?
A forward deployed engineer is the engineer a software company sends to sit with a customer's team and make the product work in their setup. Alex does that job as AI, from your team chat, on your support agent and the integrations around it.
Does Alex work with the support agent we already run?
Depends on your setup. Alex needs to read your agent's conversations and configuration, and to change what you ask it to. On the demo we go through your systems one by one and tell you straight which ones Alex can reach and which it can't.
What does onboarding involve?
One call to start, where we go through which agent you run and what it's connected to. Then we agree on what Alex may read and what it may change, and add it to your Slack channel or your WhatsApp or iMessage group. If you want more access later, you ask and we widen it.
Who controls what Alex changes?
Your team. Alex only changes the agent when someone in your channel asks, and only within the access you agreed to at onboarding. Anyone in the channel can ask for work inside that access. Nobody can widen it from the chat. That stays with Adelante.
Who in our team can use Alex, and in which language?
Anyone in the channel or group it joined, within the access your team agreed at onboarding. It answers in whatever language you write in, so a Hebrew question gets a Hebrew answer. Product names and ticket and order numbers stay exactly as you typed them.
Can Alex change integration code, or only the agent's text?
Both. It changes configuration and code in the custom integrations Adelante built for you, like an order lookup that suddenly has to cover a second store. Before it reports back it runs the integration's automatic checks and replays the ticket that kicked it off.
Can Alex send us a weekly report automatically?
Yes, if you ask for one. Nothing recurring runs by default. Ask for a Friday report and Alex confirms the time and the channel it'll post to. If scheduling fails, it tells you in the thread, so you're never waiting on a report that isn't coming.
Does Alex talk to our customers?
No. Your customers talk to your support agent. Alex talks to your team, about that agent, in your channel. It reads customer conversations when it's investigating something, and that's as close as it gets. It never writes to a customer or edits a ticket, and the channels your agent answers on are off limits to it.
How does Alex relate to Adelante?
Adelante builds and runs Alex. If you're on the managed service, Adelante runs your support agent and Alex is how your team asks for changes to it. Whatever sits outside Alex's reach goes to Adelante's engineers. On its own, Alex works on the agent you already run. Either way you get your own Alex.