“I filled out the claim form” sounds like a finished task. For a traveler who canceled because of illness or injury, it may mean only that the first record exists. The evidence may still be incomplete, authorization may be missing, and the benefit administrator may not have received anything.
TourClaim by Copernican is built around the work that follows intake: reviewing credit-card travel benefits, collecting supporting documents, coordinating medical-provider evaluation when needed, preparing and filing the claim, and handling follow-up. For a personal agent, the challenge is knowing which of those steps has actually happened.
One canceled trip can involve several kinds of proof
Take a fictional $900 booking canceled after an injury. The merchant returns $200. The traveler’s remaining loss is $700 before any coverage decision. The confirmation proves the reservation; the payment record shows how it was paid; the refund record explains why claiming the original $900 would be wrong.
The medical documentation serves a different purpose: supporting the reason for cancellation. The cancellation policy and correspondence help explain what the merchant retained. A signed authorization establishes what Copernican may do for the traveler. No single document answers all of these questions, and the $700 is not a promise of reimbursement.
A useful assistant preserves these distinctions. It should report an unknown refund amount as unknown and ask for the record. It should hand a missing clinical document to a process that can involve a provider, rather than filling the gap with generated text.
“Submitted” has to name the recipient
Our connector status reference separates a draft from a claim and an intake from an insurance filing. This is the distinction an assistant should preserve in its updates:
| Record or status | What the traveler should understand |
|---|---|
| Saved draft | Answers have been saved. Missing information or authorization may still be required. |
ready_to_submit | The draft has been signed. It is ready for the authorized submission step. |
INTAKE_RECEIVED | Copernican has received the intake. This is not proof that the benefit administrator has received a filing. |
MED_NOTE_REQUIRED or MED_NOTE_IN_PROGRESS | Medical documentation is part of the remaining work. A note has not necessarily been issued. |
SUBMITTED | The claim has been filed with the benefit administrator. Filing is not approval or payment. |
Current integration limit: review-mode API claims stay at INTAKE_RECEIVED in an isolated synthetic environment. No insurer filing, billing, or clinician evaluation happens there. The later statuses describe the service workflow; testing the connector does not run those steps.
The draft state submitted means that an intake became a claim record. It is distinct from the claim status SUBMITTED, which describes filing with the benefit administrator. Relay the API’s next_action and current mode instead of collapsing both into “your insurance claim is filed.”
Authorization must follow the actual evidence
Suppose a traveler signs, then another receipt arrives. The claim now contains information the traveler has not approved. In the connector, editing answers or importing evidence invalidates the earlier approval; the traveler reviews and signs again.
This matters for agents that gather information over several messages. “The traveler approved earlier” is not enough when the draft has changed. The authorization page and the API’s revision and approval rules make the next step explicit.
Recovering from an interruption should preserve the claim
A network timeout can leave an assistant uncertain whether a save or submission succeeded. Starting over may create conflicting records. TourClaim’s connector uses creation keys, revision checks, evidence deduplication, and submission retries that return the existing claim.
Those controls let an integration recover by reading the saved state and continuing. An outdated edit is refused so the assistant can reconcile it with the latest answers. The public CLI and SDK repository and agent instructions give builders a concrete place to start.
The service behind the status
After a real intake, Copernican reviews the benefit terms and supporting evidence, works on missing documents, files the claim, and follows up on requests for more information. A provider decides whether medical documentation can be issued. The benefit administrator decides coverage and reimbursement.
We are building a handoff that connects an agent’s prepared intake to the people and processes needed to move the claim forward. A personal assistant can remain the place a traveler asks for help, while Copernican handles the specialized work and the traveler retains the decisions only they can make.
Explore the assistant pages and example journeys, or read how we address the medical-documentation gap. For a real claim today, use the traveler’s secure online form.
Build a travel-claim handoff into your agent
Follow the production-access request process and tell us your product, website, use case, expected volume, and intended launch date. Copernican reviews requests and replies by email. A request or a self-service test key does not activate live access; each traveler must still authorize their own connection.
Start with the public source repository, developer guide, and current interface status. Self-service integration testing uses fictional data in synthetic review mode; nothing is filed, billed, or sent to a clinician.