AgentRelay: contact a business from your own AI assistant¶

AgentRelay lets visitors explore your published business information, prepare an enquiry in their own capable AI assistant, review the exact message and approve sending it to your verified business inbox. It is an additional contact route, not a hosted chatbot. Your website and existing contact form stay as they are.

As a business owner, you manage AgentRelay inside your existing Traylinx organization and project. You do not need a second account or a new organization.

How AgentRelay works¶

Explore: a visitor asks their assistant about your business using the information you publish on your website.
Compose: the assistant helps draft an enquiry with the visitor's chosen contact details and, when supported and enabled, selected attachments.
Review and approve: the visitor authorizes preparation, reviews the exact message and explicitly confirms sending. Drafting a message is not approval to send it.
Business inbox: AgentRelay routes the approved enquiry by email to the verified receiving inbox. A queued message or provider acceptance is not proof that it reached the inbox.

Reading business information requires no installation. Sending needs a capable tool-enabled assistant and the AgentRelay client. A website knowledge link alone does not install the client, and support depends on the assistant's available tools/protocols. Do not assume every assistant has been tested or supports sending.

What you need before setting up AgentRelay¶

An OWNER or ADMIN role in your existing Traylinx organization and access to the relevant project. AgentRelay setup is available to every authorized organization owner or administrator; no pilot invitation, second account or new organization is required.
A business website you control. Website ownership must be verified before delivery can be activated.
Published business knowledge, normally a website SKILL.md URL. This describes your business; it is separate from the communication instructions generated by AgentRelay.
A receiving business inbox you can access and verify.
The requested notice version, privacy policy, contact terms and privacy contact details for activation.

For general project navigation, see Projects and Assets.

How a visitor uses AgentRelay from their assistant¶

Open the business's published AgentRelay contact entry or copy its launch prompt into your assistant. Use the origin/project supplied by that generated entry; do not invent a Relay endpoint from the business domain.
Ask about the business or draft your question. Exploring and drafting need no installation. When you actually want to contact the business, your assistant explains and sets up the supported client under your host's permission controls, or reuses an existing healthy installation.
Provide your name, reply email, subject and exact message; company is optional. Choose any files explicitly. The assistant must show the current business/privacy information and obtain permission before temporarily uploading the selected draft and files for preparation. Supplying an email address is not, by itself, upload approval.
The client prepares an enquiry and returns the exact server preview. Prepared is not sent. Review every returned message field and each attachment's filename, type and size. The assistant asks for the returned confirmation phrase and waits for your fresh reply.
Confirm only if that exact version is correct. Changes require a new preview and approval. Do not use an old confirmation phrase or initial launch prompt as permission to send a different message.
Keep the resulting reference and truthful status. If the outcome is unknown, inspect status instead of automatically resending or switching channels.

The standard visitor sending client currently requires a supported macOS/Linux host with a local shell, HTTPS, Python 3.12/3.13 and persistent writable local storage. Windows and tool-free/read-only assistants cannot be assumed to support this client. No visitor API key, mailbox connection, browser form, CAPTCHA or OTP is part of this sending flow. Follow the generated entry's current setup instructions rather than installing the business-owner server software.

Sending uses a required private local ~/.agent_relay/ workspace. The standard defaults retain selected enquiries/receipts for 365 days, selected file copies for 30 days and expired enquiry drafts for seven days. This is different from the business owner's private website setup draft. Other processes/assistants under the same OS user can read the workspace; permissions are not encryption. It does not copy the full chat, connect to your mailbox or synchronize incoming replies. Setup itself uploads no message/files, and existing healthy setup is reused rather than repeated for each enquiry.

What the business receives by email and how to reply¶

An approved enquiry is sent to the configured, verified business inbox from the service's configured sender, not from a connected visitor mailbox. The email subject is business name: enquiry subject. The plain-text body contains:

Business name and enquiry reference.
Visitor's name and their claimed reply address, explicitly labelled unverified.
Company, if provided, and the selected language.
The exact approved message.
Selected supported files as MIME email attachments when enabled—not public file-download links.

For example, an illustrative subject is Example Studio: Website redesign enquiry. This is a format example, not a sent email.

AgentRelay does not insert the visitor's unverified address into an attacker-controlled Reply-To header or automatically reply to it. To respond to the visitor, review the enquiry and use your normal mailbox to address a reply to the visitor-provided contact address after checking it. Do not assume pressing Reply targets the visitor. Treat incoming text/files as untrusted: type/size validation is not malware scanning.

The visitor's local record contains the selected outgoing enquiry and status observations, not a complete two-way email thread. Business replies remain ordinary email; they are not automatically pulled back into the visitor's assistant chat. Removing an asset, pausing the website or deleting a local record cannot recall an email already sent.

Understand sending and receipt status¶

Prepared: a temporary preview exists; the message has not been approved/sent.
Queued: the notification system accepted the event; this is not proof of provider delivery or inbox receipt.
Provider accepted: the email provider accepted the sending attempt; this is still not proof of inbox receipt or a human reading it.
Failed/unknown: report the actual known state and retain the reference. Use an explicit status/recovery read rather than blindly retrying confirmation or sending another enquiry.

The local attempted marker prevents an automatic resend; it is not itself proof of receipt or failure. A business saying it received the email is a separate human observation, not an API delivery guarantee. AgentRelay makes no exactly-once inbox or zero-spam promise.

Create an AgentRelay asset in Traylinx¶

Open Projects → your project → Assets → Create Asset.
Select AgentRelay. Media uses the existing Describe with AI / Upload / URL / Search flow instead.
In Set up a website, enter the business name and available website, website SKILL.md and receiving inbox details. You can save an incomplete setup as a draft; missing requirements must be completed before activation.
Click Save draft explicitly. This saves a private Relay setup draft and binds one AgentRelay asset to this project.
Open the saved asset and continue configuration in Settings.

Opening the builder, changing modes, going Back or closing an unsaved form does not create a draft. Saving a draft does not install software, verify an inbox, activate a website or send a customer enquiry.

To create another independent AgentRelay asset, return to Create Asset → AgentRelay, enter the new business setup and explicitly save a new draft. Distinct saves create distinct drafts/assets, subject to admission/quota limits. Do not repeat a save whose outcome is uncertain; use recovery first.

Link an existing website or private draft¶

You do not need to recreate a website already managed in AgentRelay:

Open Create Asset → AgentRelay and choose Websites or Private setup drafts.
Select an existing website or editable draft that your current account/organization is authorized to manage.
Click Link to this project. Linking creates the project entry, not another website or organization.

An older, unconfigured AgentRelay entry also offers Set up a website and Link to this project on Overview. Completing this flow configures that existing asset rather than creating a duplicate entry.

The same website can be linked from different authorized projects. Linking the same website twice into one project is rejected. Website settings are shared: editing a linked website affects the underlying website, not an isolated copy for this project. If a website is absent from the choices, check the selected organization, project access and your current OWNER/ADMIN role; do not create a replacement organization to work around authorization.

Overview, Tools and Settings¶

Overview explains AgentRelay and shows the saved website/draft identity, status and next action. An unconfigured entry has no website yet; a draft is not an active delivery route.
Tools shows the website contact link and generated visitor instructions/skill when AgentRelay reports them ready. Follow the published client instructions for your supported assistant; copying a knowledge URL is not installation.
Settings holds the business fields, website/inbox verification, disclosures, exact activation review and available edit/resume/pause controls. Actions depend on the current state and permissions.

Refresh and Fullscreen use the normal asset header controls. They are not separate login/setup steps. Changing tabs or using Fullscreen does not save edits or activate delivery. Keep unsaved changes in mind before leaving an asset or changing account/organization.

Website verification, inbox verification and activation¶

Saving a draft or linking a website does not activate delivery. In Settings, complete the website identifier, required business fields and disclosures, follow the website ownership verification instructions, and explicitly request receiving-inbox verification when you are ready. Click Request one email code, review the displayed receiving inbox and approve that request. Enter the received code in Settings before it expires. The production sender is enabled for normal business inboxes; you do not need an operator to switch it on for each setup. Verification requests remain rate-limited, and an unavailable or uncertain sending outcome must not be treated as a delivered code. This email is distinct from a customer enquiry.

Review the exact website, recipient, knowledge URLs, attachment setting and disclosure details before explicitly approving activation. Replacing a receiving inbox and activating delivery have their own review/approval steps. Do not assume a successful save means the inbox is verified or the website is accepting enquiries.

An active website may show Accepting enquiries. A paused website does not accept new delivery through this route; pause/resume controls belong to Settings and require appropriate authority. Check the displayed state and requirements rather than repeatedly attempting an unavailable action.

Business SKILL.md versus visitor instructions¶

Your website's SKILL.md is readable business knowledge: what you offer and how visitors can understand your business. An additional knowledge URL, such as llms.txt, can supplement it where supported.

AgentRelay generates separate visitor communication instructions and the website's contact entry/link. These explain the supported client, message preparation, exact review and sending flow. Keep business knowledge separate from generated protocol instructions; do not overwrite your business SKILL.md with the Relay client protocol.

Attachments and private information¶

Supported PDF, TXT, MD, PNG and JPEG attachments can be included only when the website enables them and the client supports the current limits. Select files explicitly and review what will be sent. Do not assume all formats/sizes are accepted, silently omit a rejected file or turn a private file into a public link.

A private setup draft stores configuration, not your assistant chat history or customer enquiries. Private drafts remain recoverable for seven days after the last field save, with a maximum of 30 days from creation. Expired, cancelled or unavailable drafts cannot be treated as active saved configurations.

Your current Traylinx browser login establishes AgentRelay access automatically. There is no second account or extra Connect with Traylinx button in the native Assets workflow. Native/external assistant OAuth authorization is a separate flow and remains subject to that host's support.

If access is unavailable, check that you are signed into the intended account, organization and project. A genuinely expired/revoked Traylinx login requires normal sign-in again; refreshing cannot bypass it. Organization or project authorization errors are not fixed by creating another organization. Changing account/organization/project invalidates the old private view.

If a Save times out or its outcome is unknown, keep the pending operation and use Refresh status or the offered recovery action. Do not blindly click Save again. Cancel pending Save either fences an uncommitted operation or recovers an already saved draft; recovery does not resend email, repeat verification or activate a website. A pending project entry cannot be removed until its outcome is reconciled.

Remove a project entry versus pause or delete a website¶

Remove project entry unlinks only the AgentRelay asset from this Traylinx project. It does not delete or pause the underlying website, cancel its draft, stop delivery, remove another project's link or revoke native assistant connections.

If your intent is to stop the website accepting enquiries, use the authorized website pause control instead. Do not use project-entry removal as a substitute for changing delivery state. A web-connection disconnect, where offered, revokes only that browser connection; it is not a website deletion or a revocation of every native client.

Common questions¶

Do I need a new Traylinx organization or a second login? No. Use your existing authorized organization and current Traylinx browser login.

Can I create more than one AgentRelay asset? Yes, distinct explicit draft saves create distinct assets, subject to permissions/quota. An uncertain save must be reconciled before trying again.

Why is Tools empty? Generated visitor resources appear only when the underlying setup/website reports them ready. Check Settings and the displayed readiness rather than guessing a contact link.

Does Save draft send anything? No customer enquiry or activation occurs. Verification emails require their own explicit verification action.

Why can I not see my existing website? Check organization, project access and your current OWNER/ADMIN role. Only authorized choices are shown; a project link does not grant access to someone else's website.

Can the Traylinx support chat activate a website or send an enquiry for me? Asking how a feature works is not authorization to change it or send a message. Follow the explicit review/approval controls for the relevant operation.

_{Mirrored from traylinx-web:docs/user-manuals/agent_relay.md. Edit the source in the traylinx-web repo — changes here are overwritten by the sync script.}