One job and its limits
A website assistant can explain services and help visitors prepare an inquiry. A staff workspace can organize context and prepare an editable response. An internal tool can help turn repeated information into a structured draft. These are different jobs and should not inherit the same access or authority.
Choose a task for which the business already has reliable information. Define what a good result looks like, which questions the system may answer and when it must ask for more detail or involve a person.
Knowledge someone can maintain
Review service descriptions, approved claims, contact routes and exceptions before connecting a public assistant to them. Old proposals and internal notes can contain expired commitments or private material. The public knowledge set should include only information appropriate for those visitors.
Assign a person to update material when prices, services or policies change. Keep the business source separate from the instructions controlling the assistant’s behavior. A customer’s message should not be able to grant new permissions or change the approved offer.
The point where a person takes over
Plan how the conversation reaches the next person. A summary may go into an inquiry form for the visitor to review, or into a reply draft for staff. Preserve the original message and show which action still needs a person's decision.
If the answer requires a custom quote, unavailable knowledge or an account-specific decision, the interface should explain the next step. Avoid making the visitor repeat information unnecessarily. Also avoid claiming that a message was sent or a record was saved until that action actually completed.
Questions, exceptions and failures
Use representative questions, ambiguous requests and examples outside the approved scope. Check whether the assistant distinguishes facts from uncertainty, preserves important details and reaches the correct handoff. Test service outages and failed notifications as well as successful conversations.
Review costs, response time and the information sent to external services in the context of the project. Keep test records separate from customer work. An appealing demonstration is a starting point; dependable operation requires repeatable checks and someone who reviews exceptions.
Our development tools and responsibilities
Our work includes AI-assisted development through OpenAI Codex. The HTSG website project uses GPT-6 Astra in its development workflow. We judge that process by the implementation and its verification. A model name does not establish the quality of the finished system.
Tools and models can change between projects. We document the tools actually used and the behavior actually tested. We do not assume that using a coding agent establishes an endorsement, removes engineering responsibility or proves a business result. The product remains accountable to the people who use and maintain it.
- Choose one task and name its operating owner.
- Keep approved knowledge current and permissions explicit.
- Provide a working human handoff.
- Evaluate ordinary, uncertain and failed interactions.
