AwraIQ, Help Center, and Customer Success

Public support is not only a help page. AWRA has public docs, help center articles, glossary entries, Academy courses, release notes, roadmap pages, tools, industry pages, and assistant knowledge that all help users learn before they need a ticket.

The practical goal is simple: when a buyer, partner, vendor, or user asks a common question, the answer should be findable, current, and linked to the next useful action.

In practice, follow one question through the system. A finance lead searches the help center for “VAT return”. The search reads one public knowledge index built from help articles, blog posts, public pages and Academy courses, so the answer can come from whichever explains it best: the help article gives the steps, the glossary defines a term like input tax, and the Academy course teaches the routine and ends in an assessment with a certificate anyone can verify by its code. AwraIQ, the assistant on the public site, answers from the same knowledge. If the same question keeps arriving and the answer is thin, that is the signal to improve the article or course, not to answer it by hand again.

AwraIQ should guide, qualify, and route. It can answer public questions, summarize next steps, point users to docs, and hand off when a person needs to act.

The handoff matters most. A user should not repeat everything when the assistant has already collected the page, module, error, expectation, and contact context.

In practice, when a visitor asks AwraIQ something it should not settle alone, such as a security questionnaire, a migration estimate or an account problem, they use Send AWRA a message. The handoff records a topic (pricing, demo, migration, security, enterprise, support, integration or general), an urgency from low to urgent, the page they were on, and the assistant’s intent, confidence and reason for handing off, with the last twelve messages of the conversation attached. While a representative is online, live chat sits above that form, and a website chat shows the representative the visitor’s recent AwraIQ messages as well. If nobody accepts within about three minutes, the chat is marked missed and goes to the support inbox, and the reply comes by email. Either way, the person explains once.

Customer success is not just checking whether people logged in. It is helping the customer reach operational maturity: cleaner data, fewer stock surprises, faster approvals, better cash visibility, and stronger reporting trust.

The best success review uses real signals: adoption by module, open exceptions, report usage, overdue workflows, support themes, and the next Academy courses the team should complete.

In practice, a quarterly success review can be built from screens the customer already has. The Admin Command Center shows setup progress, incomplete controls such as admins without multi-factor authentication, and stale configuration. Automation Insights shows the workflow success rate, failing workflows and overdue workflow tasks, and each module’s Overview shows its own exceptions. Pick the two or three signals that matter most to this customer, agree one behaviour to change by the next review, for example closing the month through the checklist rather than around it, and name the Academy course the responsible people should complete before then.