Your org has been invited to partner with a hotline.

Transfur Line is a disaster-response coordination platform built for animal rescue organizations. Other orgs run hotlines on it — phone numbers that take calls and texts from the public when something is going wrong. Operators at the hotline-owning org triage what comes in, respond where they can, and hand off the rest.

When a request needs work the hotline-owning org doesn't do — a vet emergency, a wildlife rescue, transport, a sister org's specialty — that's where partner orgs like yours come in. Someone has invited you because they expect their hotline to receive cases your team can handle, and they want a clean way to route those cases to you instead of phone tag and email chains.

A partner is another organization or agency the hotline owner can hand off work to. There are two flavors:

• Accepted partner: you're on Transfur Line, you've accepted the invitation, and you can receive dispatched tasks like a peer.
• Shadow partner: you're listed but haven't joined the platform yet. The dispatching org can still track work directed at you ("called this clinic, awaiting response"), but you don't see anything until you accept.

Right now you're probably a shadow partner. The next step promotes you to accepted.

Click the link in the invitation email. If your org isn't on Transfur Line yet, you'll create an account and your org at the same time — partner orgs don't pay anything; the hotline owner covers the platform cost. If your org is already on the platform, you'll sign in and accept on its behalf.

After acceptance, the relationship is live: the dispatching org can route tasks to you, and you can see those tasks in your dashboard. Nothing happens automatically — you're just opening the door.

You're the contact, but the people doing the work probably aren't just you. From your org's Members page, invite the people who'll respond to dispatched tasks — the vet, the rescuer, the driver, whoever it is. The role hierarchy is Owner → Admin → Member; most teammates come in as Members.

For finer-grained access (say, "only the surgical team sees surgery tasks"), group Members into Teams — small named groupings within your org that the dispatcher can target directly.

When work is dispatched to your org, who gets emailed? Each member of your org sets this for themselves. Some orgs want everyone notified for every task; others prefer a small triage group that picks up first and routes internally.

Have your team set their preferences once at the start, before traffic ramps up. It saves a lot of inbox annoyance later.

Dispatched work shows up as tasks on your dashboard — not as messages or conversations. Each task includes the case description, a due date if there is one, who at the dispatching org sent it, and a link back to the source conversation so your team can see the original context.

Tasks can be assigned to your org as a whole, to a specific team, or to a specific person — the dispatcher decides. Either way, anyone with access can open the task, see the full picture, and either pick it up or comment back with a reason it's not a fit.

Open the task, do the work, and leave a comment with what happened — a vet visit summary, a transport note, "couldn't reach the animal." Then move the task to COMPLETED. The dispatching org sees your status and your comments in real time; no separate emails or status reports needed.

Task statuses are TO_DO → IN_PROGRESS → COMPLETED, with BLOCKED for "we can't move this forward right now." Move them as you go — the dispatcher uses these to know whether to wait, follow up, or send the work elsewhere.