Provider routing

When an agent team builds a business, the providers that business uses start talking back: a customer pays, an email is answered, a post gets a comment. Those events have to reach the team that caused them, and a website the team deploys has to call the providers under that team's name. I built three small tools for that wiring. None of them takes a work order as input. The work order, its team lead and its execution come from the caller's identity, so an agent can only wire its own work.

The tools

register_provider_inbox sends the provider events that belong to the current work order to its team lead's mailbox.

create_website_runtime_binding binds a deployed website to chosen provider connections for the current work order, each in its sandbox, live or shared environment, so the site's provider calls are attributed to that work.

register_inbound_email_route connects an existing inbound email address and receiving domain to the current work order, so mail sent to it reaches the team.

These sit beside the payments, email and CRM and social-publishing groups. Those groups let a team act on a provider, and these tools close the loop when the provider answers.