# Multilingual event attendee support: routing worksheet

Copy this sheet for each event. Record real coverage; do not infer a language from a name, country or browser setting.

## Channel coverage

| Language | Web form | Email | Phone | On-site desk | Hours/time zone | Fallback and owner |
|---|---|---|---|---|---|---|
| [language] | [yes/no + URL] | [address] | [number] | [location] | [hours] | [named route] |

## Case routing

| Case reference | Event/edition | Attendee's preferred reply language | Issue category | Urgency and event deadline | Language-capable responder | Decision owner | Next action and due time | Safe reply channel | Last update | Resolution |
|---|---|---|---|---|---|---|---|---|---|---|
| [internal ID] | [event] | [ask attendee] | [registration/ticket/access/travel/change] | [specific] | [person] | [team] | [action/time] | [channel] | [time] | [outcome] |

## Handoff check

- [ ] Attendee has an acknowledgement in a language they can use, with an honest response window.
- [ ] The case contains only details needed to resolve it; payment data and unnecessary sensitive records are excluded.
- [ ] Language responder and decision owner are both named.
- [ ] The next team can see verified facts, previous replies and the next step without asking the attendee to repeat everything.
- [ ] Urgent on-site or entry cases have an immediately usable contact.
- [ ] Consequential translated replies receive a meaning check before sending.
- [ ] Resolution and public FAQ changes are recorded separately.

This is an operations template, not a promise of live service in every language or a substitute for local privacy and policy review.