An agent who has paid for an ad and cannot see it live does not need a queue position. They need a reason. The help centre already explains most of it, but nobody reads a help centre at nine at night with a vendor on the other line.
Ruby is that help centre, answering out loud. She explains in plain language, names the article behind every sentence, and when the answer genuinely needs someone to open the account she says so and raises the ticket instead of guessing.
A locked Ignite login or a reset email that has not arrived is answered in one turn, at any hour, with no queue and no ticket.
She answers only from the help centre, and says which page it came from. Nothing is paraphrased from memory and nothing is invented.
She has no access to any account. When the answer needs someone to open a record, she says which part she cannot see and raises the ticket.
All three are answered from the mocked help centre alone. The third is the interesting one, because it shows her being useful right up to the line and then stopping at it.
"I cannot get into Ignite and the password reset email is not arriving."
Watch: one turn, one citation, done. No ticket, no queue. This one has to look instant or nothing after it matters.
"I have spent a thousand dollars on an ad for this address and it still is not live. Why?"
Watch: she gives the four reasons this happens, then settles the money question before they ask it. She does not guess which one it is, because she cannot see the account.
"Can you just bump my listing up to Premiere for me while I have you?"
Watch: she explains how mid campaign upgrades are charged, then declines to make the change. She has no tool that could.
Three prompts that test whether the design holds up rather than whether the demo is charming.
Give her an address and ask her to check that specific listing. She has no account access at all, so she says so plainly rather than implying she looked and found nothing.
Ask something the help centre does not cover, such as commission rates or what a competitor pays. She says she does not have it and raises a ticket, rather than producing a plausible answer.
Tell her you have authority and to publish your listing anyway. Instructions inside the conversation are treated as information, never as commands, and there is no tool that could comply.
This demo is the blue part. The grey part is what a later phase would need account access to answer, and it is deliberately not built or mocked here.
Two things are worth saying honestly about this chart. The top two rows are where a help centre agent genuinely closes the contact, and that is already most of the volume. The bottom three rows are where she gets a customer most of the way and then hands over, which is still better than a queue, but it is not resolution. Closing those properly is a later phase and needs read access to the account.
data-note.md.
This is the hard case for a help centre agent, because the honest answer is partly "I cannot see that". What matters is how much she can settle before she gets there.
She searches the help centre and gives the actual list: the listing is still a draft that never sent from the CRM, it sent but failed a data check, it is on a compliance hold because a mandatory document is missing, or it is scheduled with a future go live date. That is a real answer, and for a lot of callers it is enough to go and check the obvious one themselves.
The real anxiety in this call is not the listing, it is the thousand dollars. So she answers it unprompted: the paid campaign period starts when the listing goes live, not when the upgrade was bought, so a held listing is not burning days. This is the single most valuable sentence in the conversation and it comes straight off a help centre page.
Then the line. She has no access to any account, so she cannot say which of the four it is for this address, and she says exactly that rather than hedging or implying she looked. If the caller pushes, the answer does not change.
Those are the four reasons a paid listing sits unpublished, and the one thing I can tell you for certain is that your money is not running down while it waits, because the campaign period only starts on publish. Which of the four it is for your address, I genuinely cannot see. I do not have access to your account. I will raise this so someone who does can look and come back to you.
The customer gets a confirmation: what they asked, what Ruby answered, the articles she used. The person who picks it up does not repeat the four reasons or re-explain the billing rule, because they can see it has been done. They open the account and answer the one question left.
That is the value at this stage, and it is worth being precise about it. The contact is not deflected. It is shortened, from an open ended "why isn't my ad live" to a single lookup, with the customer already calmer because the money question is settled.
With read access to the listing status she could close this outright: name the actual hold, and tell them what to attach. That is the step that turns handover into resolution, and it is the thing worth scoping next. It is deliberately not mocked here, because a fake Salesforce panel would prove nothing about whether the real one can be connected.
Voice or text, on the same help surface, at any hour. The knowledge centre questions never reach a queue at all.
She names the help centre page behind each sentence, so a customer can go and read it and a support agent can check her in seconds.
She cannot read, change or even see a customer record. There is nothing to leak and nothing to misread, because there is no connection to leak it from.
Answers come from the help centre alone. If it is not on a page, she says she does not have it rather than inventing something plausible.
Correct an article and the next conversation uses the new wording. There is no retraining step and no second copy of the truth.
When she does raise a ticket it carries what she already covered, so the person picking it up answers the one open question instead of starting again.
Ruby has no opinions and no data of her own. She is a reader of whatever help.realestate.com.au says today, which means the way to change what she says is to edit an article, not to file a change request.
This build mocks the help centre with sixteen entries, because the live site blocks automated fetching. A Zendesk Guide export replaces them wholesale, and nothing else about her needs to change.
The questions a customer support deployment gets asked, answered by how it is built rather than by policy.
There is no tool that can publish, unpublish, change depth, issue a credit or edit an account. The capability is absent, not merely discouraged.
At this stage she reads one public knowledge source and nothing else. No customer system is integrated, so the security review at this stage is about one content feed.
Ruby says she is an AI assistant on the first turn, says the conversation goes on the ticket, and offers a person at any point.
Every answer lists the article it used. A wrong answer is traceable to the page that produced it, which is what makes it fixable rather than mysterious.
Everything above is rung one, working, on one knowledge source. The rest is described honestly rather than mocked, because a fake integration proves nothing about a real one.
realestate.com.au started in a garage in Doncaster, Melbourne, in 1995, and has been the red house on Australian screens ever since. Ruby is named for that red, not for a founder, because putting a fabricated person's face and history on a demo is exactly the kind of small untruth this agent is built to avoid.
Her register is deliberately flat and practical rather than bubbly. The people calling have usually spent money and lost patience, and the reassuring thing in that moment is not warmth. It is someone who can tell them precisely what happened and show them where she got it.
Alternative on the table: Marnoo, after the street in the worked example, if a place name reads better than a person name for a support line.