Ten questions, a hundred times
Delivery, sizing, stock, returns, opening times. Typing those out personally is not customer service, it is transcription — and the better a post performs, the more of it there is.
The same ten questions arrive a hundred times a week, and the answers are already written on your own site. An agent handles those in under a second, shows where each answer came from, and hands the rest to a person with the thread attached.
Free to start · No credit card · Official Meta API
Hey, do you ship to Ireland?
We do! Orders to Ireland arrive in 3–5 working days, and you’ll get tracking as soon as it leaves us.
northlane.co/shippingWhat’s your return window?
You have 14 days from the day it arrives. Anything unworn with the tags still on can go back, and returns are free within the UK.
northlane.co/returnsMy order turned up damaged :(
I’m sorry about that. I’ve passed this to the team with your order details and someone will come back to you to sort a replacement.
handed to a personTwo of these never reached a human. The third was tagged and assigned to someone who can fix it.
Why automate this
A post that does well does not bring you more orders so much as more questions, and they are almost always the same ones. Three things make this worth handing to an agent, and only one of them is about what time it is.
Delivery, sizing, stock, returns, opening times. Typing those out personally is not customer service, it is transcription — and the better a post performs, the more of it there is.
Every reply names the page or document behind it. Automation you cannot audit is a liability waiting to happen; an answer with a source attached is one you can check and correct.
Evenings and weekends are when people browse and ask. A reply in a second at midnight beats a considered one at nine, because by nine they have asked a competitor the same thing.
The play
Support automation nearly always fails in the same place. It answers the easy thing confidently, and then has nowhere sensible to put the hard thing. All four stages have to exist for it to be safe to switch on.
northlane.co · 47 pages
returns-policy.pdf · 9 pages
Shopify · 212 products
Stage 01 · the sources
You are not writing answers from scratch. You are pointing the agent at the ones you have already published, and policy pages beat marketing pages every time.
ⓘ northlane.co/shipping
Stage 02 · the answer
Any tool can reply quickly. What makes an automated answer safe to send is that you can see which page it came from, so a wrong answer is a document to fix rather than a mystery to investigate.
→ assigned · tagged order status
Stage 03 · the boundary
Anything about one specific customer — where their parcel is, whether they get a refund — is not in your policy pages and never will be. The agent does not improvise. It stops.
Assigned · order status
Agent handled 24 before this
Stage 04 · the queue
Handover is where most support automation becomes worse than none, because the customer is made to start again. Here the thread arrives whole, with what was answered and why it escalated.
Most tools stop after stage two. They answer the easy question well, then answer the hard one just as confidently, because nothing was ever built to catch it.

What you get back
Every conversation lands in one queue, labelled with what is driving it — an agent, a workflow or a person. Nothing happens in your DMs that you cannot read back, which is the difference between delegating support and losing sight of it.
Threads carry their full history, so anyone picking one up has the context already. And everyone who messaged becomes a contact with whatever the conversation collected, which means a support queue quietly builds the same list a lead form would.
The agent
An agent is exactly as good as what you point it at, and exactly as safe as the boundary you draw around it. You set both.
Answer from your own sources
Your website, your Shopify store, or a PDF such as a size guide, price list or returns policy. It answers from those and nothing else, so it cannot invent a returns window you never published.
Show where every answer came from
Each reply names the page or document behind it. When something is wrong, you fix the source rather than hunting for what the bot decided — and you can check its working before a customer acts on it.
Stop at what it should not answer
Order status, refunds, anything about one named customer. None of that lives in your policy pages, so the agent does not attempt it. The boundary is the feature, not a limitation.
Escalate with the context attached
The person who takes over sees the whole conversation, what was already answered and why it stopped. Nobody asks the customer to repeat themselves, which is what usually makes handover worse than no automation at all.
Cover every channel from one place
The same agent handles Instagram DMs and comments alongside Facebook Page comments and Messenger, set up once rather than twice. WhatsApp is coming to the Business plan at no extra cost.
Answering, and knowing when not to
Custom AI agents are on the Business plan. See how agents are trained →
Proof
“Augst AI became our first-line customer support on Instagram. It replies faster than any human, and it's never off duty.”
FAQ
Related
Point an agent at what you have already written, and see how many questions never reach a person at all.
No card · Live in minutes