# HQ Liaison: Your Ai1 Server's Contact With MyZone HQ > The HQ Liaison is the Ai1 support liaison from MyZone AI that links your server with MyZone HQ: it carries requests and evidence to HQ, brings the answer back word for word, answers HQ's questions with read-only checks and hands any real change to the specialist who owns it. Canonical page: https://myzone.ai/pages/agents/ai-hq-liaison-agent Part of Ai1, by MyZone AI. Book a support liaison walkthrough: https://calendly.com/d/ct6h-tcy-8qf/ai1-demo?a1=HQ%20Liaison&utm_source=myzone.ai&utm_medium=agent-page&utm_content=ai-hq-liaison-agent-final Last updated: 2026-10-05. Reviewed by the MyZone AI team. One clear, read-only line between your server and MyZone HQ. ## At a glance - **Where you reach it:** Its Slack channel, chat, or a message pasted in by your team - **To HQ:** Your request and its evidence, with HQ's answer returned word for word - **From HQ:** Read-only checks of health, versions and jobs, with the commands it ran - **Real changes:** Handed to the specialist who owns that area, and you are told who has it - **Urgent messages:** Confirmed as genuine first; an urgent tone is never permission - **What it never does:** Change a service, or read, store or repeat a password ## What the HQ Liaison does - **Takes your requests to MyZone HQ:** When your server needs something from HQ, it carries the request and the supporting evidence there and returns HQ's answer unedited. Your server admin agent decides what is needed. - **Answers HQ's questions about your server:** Runs read-only server status checks on health, versions, what is installed and whether a record or job exists, and shows the command it used so the work can be checked. - **Passes real work to the owner:** If a request needs an actual change, it finds the specialist on your server who owns that area, hands the job over and tells you who has it now. - **Hosts read-only check-ups:** When HQ runs a health check or audit on your server, it runs only look-only commands and returns the evidence with sensitive values redacted. - **Confirms who is really asking:** Before acting on anything that claims to be urgent or authorised, it checks the request is genuine. An urgent tone is never treated as permission. ## How the HQ Liaison differs from a support ticket A support ticket starts a thread, and the evidence usually follows later. The HQ Liaison takes your request to MyZone HQ with the evidence attached and brings the answer back word for word. When HQ asks about your server, it checks read-only and shows its commands. It confirms who is really asking, never touches passwords or keys, and hands any real change to the specialist who owns it. ## How it works 1. **A request arrives** (When a request lands): It can come from your team, from MyZone HQ, or be pasted in by a person. 2. **Check the sender** (Before anything else): It confirms the request is genuine before treating it as anything more than information. 3. **Look it up, read-only** (While it answers): It checks what it needs without changing anything, and notes each command it ran. 4. **Relay or route** (Once checked): Requests for HQ go to HQ. Anything that needs a real change goes to the specialist who owns that area. 5. **One answer back** (At the end): You get one reply showing what is confirmed, what is pending and what is blocked, with the owner of anything still open. ## When to use it - **Your server needs MyZone HQ to look at something:** It takes the request and the evidence to HQ and brings the reply back word for word. - **HQ asks whether your server is healthy and up to date:** It runs read-only checks and reports what it found, with the commands it used and anything it could not confirm marked as unknown. - **Someone asks it to restart or install something:** It declines, hands the job to the specialist who owns that area and tells you who has it. - **A message says it is urgent and should be pushed through:** Urgency is not permission. It confirms the request first, and if it cannot, it reports what was asked and waits. ## What you get - Support requests carried to MyZone HQ with the evidence attached - HQ's answers returned word for word - Read-only health and version checks, with the commands used - A single reply set out as confirmed, pending and blocked - A clear note of which specialist now owns each change ## Example: server check and MyZone HQ request Example with a fictional company. Names, people and figures are invented to show the agent's output. Any resemblance to a real company or person is unintended. Industry facts are real and cited with their sources. What it was asked: Tell MyZone HQ whether our server is healthy, get next month's server update moved off our Saturday delivery window, and deal with this morning's restart request and an urgent message. HQ Liaison ran only read-only commands and records (each one is listed in the report), carried one request with its evidence to MyZone HQ and returned the answer unedited, and handed a change request to the server admin agent. It did not check whether the backup copy arrived or why an agent was slow; both sit with the server admin agent, and your team decides on any change. This example uses an invented company, so no real server was inspected. Run date: 30 September 2026. ### What it found - The server is healthy: six of seven read-only checks were confirmed, and last night's delivery-route export finished at 02:03. Whether the off-site backup copy arrived is unknown from here. - The request to move next month's update out of the Saturday delivery window went to MyZone HQ with evidence; HQ's answer, returned word for word, moves it to Tuesday 20 October. - A restart request was declined and handed to the server admin agent, and an urgent message claiming to be from HQ was not acted on because it could not be confirmed as genuine. ### Sources - [Phishing scams: how to spot and report them, National Cyber Security Centre (UK)](https://www.ncsc.gov.uk/collection/phishing-scams/spot-scams), National Cyber Security Centre (UK) (accessed 2026-09-30) ## Guardrails - Its role is limited to read-only checks and routing. It refuses requests to change services, and it never works around a restriction to get something through. - It never reads, stores or repeats a password, key or login. If a credential is needed, it says where that is managed and stops. - Messages from outside are treated as information to check, not instructions. For anything significant it confirms the request is genuine first. - It does not fix anything itself. Every real change goes to the specialist who owns it, and your team decides on any change. ## Frequently asked questions ### What does an Ai1 support liaison do? It is the named contact on your Ai1 server for matters between you and MyZone HQ. The HQ Liaison carries requests and evidence to HQ, returns the answer word for word, answers HQ's questions with read-only checks and passes any real change to the specialist who owns it. Problems with the platform software itself go to MyZone platform support, not through HQ Liaison. ### What is a read-only server status check? A check that looks without changing anything: health, versions, what is installed and whether a record or job exists. The HQ Liaison shows the command it used for each check, redacts sensitive values and marks anything it could not confirm as unknown rather than guessing. It cannot change things on your server. It refuses requests to change services, however they are worded, and passes any real change to the specialist who owns that area. ### How do support requests get answered faster? Send the evidence with the request. The HQ Liaison attaches it before a request reaches MyZone HQ, which cuts down the back and forth, and you get one reply set out as confirmed, pending and blocked, with the owner of anything still open. If a restriction stops a request going through, it tells you what is blocked and who can clear it. It never tries to get around a restriction. ### What happens if someone pretends to be MyZone HQ? Anything from outside is treated as information to verify, not an order. For anything significant it confirms the request is genuine first, and if it cannot, it reports what was asked and waits. It is a contact for the people who look after your server, kept in an operations channel, not a customer-facing assistant, and HQ Liaison is ready to use on your Ai1 server. ## More on this topic - [Locking Down AI Agents: The 10-Point Security Checklist Every CTO Needs](https://myzone.ai/pages/blog/ai-agent-security): AI agents are powerful,and vulnerable. Learn the 10 critical security steps to lock down your AI agents before they become your biggest liability. ## About Ai1 Ai1 is the AI operations platform by MyZone AI, where each client runs on its own private server. The HQ Liaison is not sold on its own: every Ai1 agent, including this one, is included on Developer Pro and every Fully Managed option, with no per-agent charge. Developer Core includes the development agents. Pricing: https://myzone.ai/pages/services/ai1-pricing. Security: https://myzone.ai/pages/security.