What covey is put to work on
Five areas for which the matching connections already ship — so an agent can work there on day one instead of having to be connected first.
Support and ticketing
A new ticket wakes the agent. It reads the history and clarifies internally what is open. Replies to customers go out only after approval.
Read onSoftware development
The agent works in its own copy of the source code. It takes an issue, submits its change for review and reads the results of the automated tests. A person does the merge.
Read onQuality assurance
The agent checks other people's changes: it reads them against the requirement, tries them in the browser and writes its findings on the change itself.
Read onEmail and mailbox
New mail in the mailbox wakes the agent. It sorts it, replies within the existing thread and files what needs filing. Outgoing mail can require approval first.
Read onFindability
The agent checks the live website: titles, descriptions, canonicals, hreflang, sitemap and structured data. It files each finding as a ticket with the URL, the current state and the impact.
Read onWhy exactly these five
Because these are the areas for which ready-made connections exist. A use case with no connected system would be a page about an intention. What is described here can be rebuilt after installation: enable the target system, hire the agent, deposit the credentials, wake it.
Try it yourself
covey is run by you: one program, a Postgres database, Docker for the workplaces. The instructions are in the documentation.