Helpful answers. A clearer way forward.

Start with common enquiries and the information needed to resolve them. A university assistant may help visitors locate programmes and official admission information; a business assistant may explain services. Defining the intended tasks keeps the project focused and makes evaluation possible.

An assistant is only as useful as the material it can draw from. Identify authoritative pages, documents and the person responsible for updating them. Time-sensitive information needs particular care so the assistant does not continue using an old notice after the institution changes its guidance.

A chatbot should have a useful response when it lacks the information to answer. The design can direct a visitor to an official page or a human team rather than inventing a detail. Sensitive decisions and commitments should remain with authorised staff.

Website, app and messaging integrations have different requirements. Provider access, user permissions, conversation retention and recurring usage costs need to be agreed. A public information assistant should not automatically gain access to private application, payment or student records.

Use a reviewed set of representative questions, ambiguous wording and questions outside the approved scope. Check both answer quality and the links or handoffs offered. Our RGU chatbot project provides institutional context, while the requirements and evaluation criteria for your assistant are agreed separately.