Give it event context
Tell the assistant where it will be, who is attending and which questions matter most, from local open days to international recruitment.
Help visitors and prospective applicants find clear answers using the knowledge your team already maintains. Offer support in different languages and connect with your existing systems, without being tied to one chatbot or CRM platform.
Ask the Knowledge Assistant a question and see the information behind its response.
Ask a question to see which Ask CDU articles support the response.
Domestic applicants
Application pathways can differ depending on the type of course and applicant. The original Ask CDU article explains options for higher education, TAFE, international and research applicants.
Ask a question to see the supporting article here.
Not every question will have a verified answer in your knowledge base. Define what happens next, so visitors get a clear path forward instead of an unsupported guess.
Explain that the available content doesn't verify an answer. Don't invent policies, deadlines or requirements.
Invite the visitor to request a follow-up. The chat can present a form with their original question already filled in.
With an integration, send consented enquiries to a team inbox, case-management system or your preferred CRM.
Use appropriately reviewed unanswered-question trends to identify and improve missing knowledge articles.
Visitors can ask questions in their preferred language, even when the original articles are written in English. The assistant uses the same knowledge, with links back to the source.
Choose a language below and try a question in the mobile chat.
Answers depend on the information available. For important decisions, the original source remains the reference.
Bring the Knowledge Assistant to open days, education expos and international recruitment events. On a tablet, touchscreen or kiosk, visitors could explore courses, ask questions and leave their details for follow-up.
Before an open day or recruitment expo, give the assistant event-specific instructions, relevant approved information and a clear goal for each conversation. It can be tailored to the audience without starting from scratch.
Tell the assistant where it will be, who is attending and which questions matter most, from local open days to international recruitment.
Include approved event schedules, featured courses, application guidance and useful links alongside your existing knowledge base.
Guide visitors toward useful next steps, suitable follow-up questions and consent-based enquiries for the team to handle later.
Event-specific briefings and multiple assistant profiles are proposed capabilities. This demo currently uses one shared knowledge service, without configurable event profiles.
Illustrative event use case. The tablet chatbot is interactive, but lead forms, consent handling, secure storage and CRM integration are not connected in this demo.
When the chat concludes, the conversation and relevant enquiry details can be passed to your case-management system, so staff have the context they need for follow-up.
Knowledge Assistant · Mobile chat transcript
The conversation will arrive here and generate a new case record.
Starting the case record
Visitor asked: How do I enrol at CDU?
As you update articles in your knowledge base, the assistant refreshes its answers to reflect the latest information.
Explore CDU at a campus information session on Thursdays from 10 am to 2 pm. Meet the team and find out about study options.
Illustrative example using fictional welcome-session details. Automatic knowledge syncing is not connected in this demo.
Help people find answers to everyday questions without having to contact the support team. That can reduce repetitive enquiries and give staff more time for situations that need personal attention.
Make useful answers available to visitors, prospective applicants and existing contacts at any time.
Make common information easier to find before it becomes another support enquiry.
Give staff more room to handle complex or sensitive enquiries that benefit from a human response.
Change your CRM. Keep your knowledge. The assistant can draw on approved articles and documents without tying your content to a particular platform.
Let visitors ask questions in their preferred language, using the same trusted knowledge as everyone else.
Support staff can receive conversation history in the case-management system they already use, with integration and privacy controls in place.
Independent AskNode concept. A production service would require testing, access controls, privacy safeguards and ongoing content review.