Routing, referring, and cross-program transfers

You route a tip to a recipient or team from the tip’s own workflow actions. Referring or transferring it to a different program uses the same panel, but only reaches a partner program your own admin has already paired with.

Route a tip within your program

1. Open the tip and choose Route this tip.
2. Pick a recipient (a specific agency or unit in your directory) or a recipient group, which reaches every member at once.
3. Add a note. It’s required, and it travels with the routing record for whoever picks up the case next.
4. Send it.

Routing is open to any operator on your team. It doesn’t need admin rights.

Route this tip: pick the recipient, write the note.

What the recipient sees

Routing a tip does not send anything on its own. There is no email, text, or outside alert. TypVault queues a pending notification instead.

• A recipient with a portal account can sign in and see the case themselves, whenever they check.
• Otherwise, someone on your team notifies them the way your program normally does, then marks that notification as sent from the pending list so the record matches reality.

Note

The pending-notification badge is a queue to work, not proof a message went out. Nothing leaves TypVault on its own when you route a case.

Refer or transfer a tip to another program

This only works with a paired partner program. Your program admin sets up that pairing once, in settings, before any tip can move. If your program hasn’t paired with anyone yet, there’s nothing to refer to.

1. Open the tip and choose Refer to another program. This step needs program admin rights.
2. Pick an active partner from the list.
3. Choose referral (both programs keep working the case) or transfer (the destination takes it over).
4. Add a note for the destination. It’s required.
5. Send it.

The destination’s own operator has to accept before any of the case’s content crosses. A short summary reaches them first: category, rough date, how many files. The narrative, location detail, and files themselves wait for their acceptance. Nobody on the sending side can push a transfer through alone: the destination decides too.

The reporter doesn’t choose whether their tip is referred. That decision belongs to the two programs, not to them, and there’s no way for them to block it once it’s underway.

Once accepted, the case content is re-encrypted just for the destination’s own key. Only their investigators can open what arrives. The reporter’s tip code, passphrase, and message thread never travel with it. The destination gets the case; it never gets a way into your dialog with the person who reported it.

The reporter’s own case view shows that a referral happened, plainly, naming the partner program when it’s known. That disclosure isn’t something you can turn off case by case.

Caution

Closing a referred or transferred tip starts your own retention clock. When it runs out, the reporter’s dialog and reward channel here are removed for good, even if the partner program is still working the case. Use Closed After Referral, and close it only once the outcome is on file or by a deliberate call to do so.

Federation: transfers between programs.

Related

• Running a tip program
• Referrals to other programs
• Statuses and case lifecycle

If a pairing needs to be set up, changed, or revoked, that’s your program admin’s call, in settings, not something you do from a tip.