Service requests
Each request classified by rule and routed with a response-time target. Measured on time to resolution, never on volume. Replies are drafted; people send them.
I read 6 open requests from Margaret Ellison's clients on 3 channels. 1 need a callback before any money moves; 3 past target; 5 replies drafted for the team.
In production a model reads the request's free text more capably; the routing rule and the callback requirement stay deterministic.
Queue, most urgent first
| Client | Request | Type | Goes to | Time | Control |
|---|---|---|---|---|---|
| Thornbury | Client“Please wire $1.2M to the fund for the capital call on the 15th.” | Advisor, then operations | 2h left of 4h | YouCall the client back on a number already on file to confirm before any money moves. An email instruction alone is never enough. | |
| Brandvold | Client“Can you get the transfer value of my UK pension moved here?” | Advisor and wealth strategist | YouReply drafted for the team to review and send. | ||
| Alcott | Client“Set up this year's required withdrawal, paid monthly.” | Client service associate | YouReply drafted for the team to review and send. | ||
| Vasquez-Hale | Client“What happens to my old 401(k) if I don't sign the form yet?” | Advisor | YouReply drafted for the team to review and send. | ||
| Renner | Client“Our accountant needs last year's tax documents.” | Client service associate | 4h left of 24h | YouReply drafted for the team to review and send. | |
| Okafor-Lind | Client“Please change the primary beneficiary on the trust account to N. Okafor-Lind.” | Client service associate | 18h left of 48h | YouReply drafted for the team to review and send. |