Every answer has an address. Here they are.
Product documentation is in the Knowledge Center. The API and the event catalog are in the developer documentation. Everything else goes to a person at a named address, and you get a reply from that person.
Start here
Knowledge Center
How the product works, screen by screen. Setting up a connection, working the margin queue, assembling an audit response, billing a clinical encounter. It lives at help.attergo.com and it is the only place any of that is written.
Developer documentation
The canonical entity model, every endpoint, and the delivery guarantees you build against: at-least-once with a stable event id, ordered within an entity, replayable from the archive. Start at the catalog, then the API reference.
A person
Anything that is not a documented procedure or a documented endpoint. Write to support@attergo.com with your location and when the problem started, and it reaches somebody who can open your tenant with a named, time-boxed grant that appears in your own access log.
Where a question goes
| You want to know | Go to | What is there |
|---|---|---|
| How do I do this in the product | Knowledge Center | Guides, screens and step-by-step procedures. |
| What does this endpoint return | API reference | Endpoints, request shapes and failure semantics. |
| Which events exist, and when | Event catalog | The canonical entities and what emits them. |
| What changed recently | Changelog | Customer-visible changes, newest first. |
| Is something down | System status | The live status page and the incident record. |
| How do you handle our data | Security overview | Controls, tenancy, retention and the BAA. |
| I think I found a vulnerability | Disclosure policy | Scope, safe harbour and the acknowledgement we commit to. |
| Something is broken for my pharmacy | support@attergo.com | Include your location and roughly when it started. |
| Billing, contracts, adding a location | Contact | The named addresses, one per subject. |
| We are evaluating you | Book a demo | A person, a real tenant, and your own questions. |
Something missing
Every procedure is written once, in the Knowledge Center, and it is kept current by the people who change the screens it describes. You will not find a second copy of it here going quietly out of date.
If you searched for something and landed here instead of an answer, that is a defect on our side. Tell us what you searched for at support@attergo.com and the gap gets written, in the Knowledge Center, where the rest of the procedures live.
Before you write in
Support response commitments are set out in your agreement, where they carry remedies. Enterprise agreements carry a contractual one, and you can ask for it in writing during procurement.
Connect one store. We will tell you what the month cost you.
Read-only credentials you can revoke. We come back with the fills that went out under cost, the services you could have billed, and the fills an auditor would ask about.