> For the complete documentation index, see [llms.txt](https://oodlz-ai-studio.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://oodlz-ai-studio.gitbook.io/docs/inbound-agent/the-knowledge/human-escalation/fully-white-label.md).

# Fully White-Label

Every brand element in the escalation email — subject, greeting, sign-off, sender, logo, support email, website — pulled from the brand profile at runtime.

> **Zero hardcoded brand values anywhere in the workflow — point the brand profile at a new client and the escalation runs as-is.**

Every element of the escalation email is pulled dynamically from the brand profile at runtime — subject line, greeting, sign-off, sender name, logo, support email address, and website URL. There is no hardcoded branding anywhere in the workflow. Deploy it for a different brand, set the brand profile values, and the escalation emails render with the correct identity automatically.

## How It Works

When the escalation pipeline fires, the first step is a call to the brand profile. It returns the brand's full identity — name, tone, support email, logo URL, website URL, and the soft upsell line included in the email footer. The escalation email template references those fields directly: every visible string the recipient sees is a brand profile value, not a literal in the workflow.

When a new client is provisioned, the brand profile is set with their values. The escalation workflow needs no edit, no fork, no copy. It runs the new identity on the next call.

## What You Get

* One workflow shipped to every brand — no per-client edits to the escalation pipeline.
* Brand identity changes propagate at runtime — update the brand profile, the next email reflects the new values immediately.
* No hardcoded support email, logo, or website — switching domains, rebranding, or changing support contacts requires only a brand profile update.
* The same escalation experience for every brand's users — formatting, tone, and reference ID flow are consistent across deployments.