# Set up Managed Support

Configure support channels, authentication, and operations before launching your consumer program.

Work with your Stripe account team to prepare Managed Support alongside your financial product integration. This guide covers setup requirements that apply to all programs. See [Managed Support programs](https://docs.stripe.com/managed-support/programs.md) for individual program workflows and authentication factors.

## Before you begin

Before configuring support, complete these planning steps:

- Confirm [program eligibility and required coverage](https://docs.stripe.com/managed-support.md#availability) with your Stripe account team.
- Choose a [support model](https://docs.stripe.com/managed-support.md#choose-a-support-model) and agree on your service scope.
- Identify your engineering, support, compliance, and launch contacts.

## Select channels and support coverage

1. Confirm which workflows Stripe handles and which questions remain with your team.
2. Confirm live-agent hours, time zones, holiday coverage, languages, and any additional channels in your service agreement.
   - Phone is the standard live support channel.
   - Email follow-up doesn’t imply a general email intake service.
   - Chat isn’t included in the standard phone offering.
3. Confirm whether Stripe enabled 24/7 IVR card freezing (not 24/7 live-agent coverage) for lost or stolen cards.
4. For branded service:
   - Agree on your dedicated support number, service identity, customized IVR,   approved communications, and program-management channels.
   - Complete the [branded email integration](https://docs.stripe.com/managed-support/set-up.md#email-integration) if Stripe sends support communications from your domain.

### Email integration 

For branded programs, Stripe uses your company’s domain to send support communications on your behalf. The following guides describe the configurations for branded communications:

- [Connected account email configuration](https://docs.stripe.com/connect/account-emails-config.md)
- [Custom email domain](https://docs.stripe.com/get-started/account/email-domain.md)
- [Branding your Stripe account](https://docs.stripe.com/get-started/account/branding.md#other-customization-options)

Unbranded programs use standard service communications and don’t require your branded support domain.

#### Email addresses

Depending on your program, create the required addresses and authorize Stripe to configure them. Confirm applicable regulated notices and sender requirements with your account team.

| Sender address | Reply-to | Configurable sender or reply-to | Usage |
| --- | --- | --- | --- |
| `[product]-notices@[company-domain.com]` | Your support email or a no-reply address. Contact Stripe for a custom no-reply address. | No | [Regulated customer notices](https://docs.stripe.com/issuing/commercial-compliance/issuing-regulated-customer-notices.md), including dispute submission, provisional credit, and dispute outcomes. |
| `support@[product]support.[company-domain].com` | Same as sender. | Yes | Agent follow-up, dispute evidence collection, and complaint resolution. |
| `identity-verification@[product]support.[company-domain].com` | Same as sender. | Yes | Additional identity verification for account holders or applicants, including credit fraud alerts. |
| `security@[company-domain].com` | No-reply address. | Yes | Multi-factor authentication messages for support cases. |

#### Design

Stripe sends branded emails with your logo, icon, and theme colors. [Configure your branding](https://docs.stripe.com/issuing/commercial-compliance/issuing-regulated-customer-notices.md?issuing-notices-sender=stripe#confirm-branding-settings) and preview it in the [Stripe Dashboard](https://dashboard.stripe.com/settings/connect/communication/email_preview?activeProduct=issuing_notices_spend_card).
![Example of a branded Managed Support email](https://b.stripecdn.com/docs-statics-srv/assets/managed-support-email-design.118759e3b7c218b66b99bde47d12edb3.png)

#### Custom domain setup

Configure regulated notices separately from agent support email. Each uses its own domain setup process.

- **Regulated customer notice emails**: Even if you don’t use Managed Support, you still need to configure applicable regulated customer notices. For emails from `[product]-notices@[company-domain.com]`, follow the [custom email domain guide](https://docs.stripe.com/get-started/account/email-domain.md) and [Issuing regulated customer notices](https://docs.stripe.com/issuing/commercial-compliance/issuing-regulated-customer-notices.md).
- **Support emails**: Stripe uses [Amazon SES](https://aws.amazon.com/ses/) to send and receive emails for `support@[product]support.[company-domain].com` and `identity-verification@[product]support.[company-domain].com`. Complete this setup separately from regulated notice configuration:
  - **DKIM keys**: Add the keys Stripe provides to the DNS records for `[product]support.[company-domain].com`. These verify domain ownership for Stripe and Amazon SES.
  - **MX records**: Add an MX record for `[product]support.[company-domain].com` so Stripe receives replies. Use the inbound endpoint for the AWS Region Stripe specifies for your support domain, following the [Amazon SES receiving endpoint guide](https://docs.aws.amazon.com/ses/latest/dg/receiving-email-mx-record.html#receiving-email-mx-record-links). Confirm the endpoint with Stripe before updating DNS, then test outbound messages and incoming replies.

## Display support contact information

Stripe provides the approved support number and placement requirements for your program. Display the number on physical cards where applicable, periodic statements, relevant account and card screens, and help content.

You can link Managed Support from your existing support channels specifically for card or account questions. For example, add an IVR option or a chat response that directs customers with eligible disputes or complaints to call the approved number. The standard phone flow doesn’t require separate ticketing handoff integration.

Maintain a monitored support destination for questions Stripe redirects to you, such as rewards, promotions, marketplace orders, or unrelated products. Provide the destination to Stripe and keep it current.

## Configure caller authentication

Callers must authenticate before an agent can disclose private account information or perform protected actions. Implement the following data and interface requirements before testing the phone flow:

- Use Stripe APIs during onboarding to provide the account holder information required by your program.
- For migrations, provide a retroactive batch of existing account holder data using the process agreed upon with Stripe before launch.
- Keep phone number, email, date of birth, and postal code current in Stripe.
- For card products, display the last four digits of the card in your application.
- For wallet products, also display the account’s `account_last4` and the support number in the wallet interface.

The phone system attempts to identify the caller using their phone number and  [program-specific factors](https://docs.stripe.com/managed-support/programs.md#authentication-factors). If it can’t find a unique match, it requests additional approved factors, such as date of birth or postal code. An agent can confirm the email on file when additional verification is required. Higher-risk actions, such as card activation or account closure, require multi-factor authentication using the approved email on file.

Agents can’t bypass authentication to disclose information or perform protected actions. Test with current account holder data and again after changing contact information.

## Grant access

Grant the Stripe support team Dashboard access using the Managed Support role. Stripe supplies the approved agent roster. Specify the process for adding and removing agents as staffing changes, including whether Stripe can manage membership with your authorization. Grant only the access required for your supported workflows.

For branded programs, also provide access to your customer-facing application or a training environment so agents can learn how customers use your product and find self-service options.

## Establish regulated workflow processes

Agree on intake, required communications, escalation contacts, and operational responsibilities for disputes, errors, and complaints for the [regulated workflows](https://docs.stripe.com/managed-support.md#support-workflows-and-optional-services) Stripe handles.

### Disputes and errors

Provide a process in your application or web portal where card customers can submit disputes. Include relevant evidence at submission and test the intake and follow-up process with Stripe. Managed Support submits disputes that customers initiate through phone support.

Wallet dispute API intake isn’t supported. Direct consumers to initiate wallet disputes through phone support.

### Complaints

1. Train your support staff and automated channels to identify and promptly route complaints to Managed Support. Examples include allegations of financial loss, discrimination, fraud, or mishandled disputes, and threats to contact a regulator or take legal action.
2. Direct the customer to the Managed Support phone line for intake.
3. Add routing instructions to your IVR, chat responses, and support procedures.
4. When direct routing isn’t possible, use the exceptional email route agreed upon during onboarding. Provide a monitored support email address for Stripe to allowlist for these exceptions. Don’t use this route as routine email intake or maintain monthly complaint trackers in place of prompt routing.

Stripe documents eligible complaints, handles or coordinates resolution, and completes applicable bank reporting. Your team continues to handle unrelated company-specific complaints.

### Escalations

1. Provide a monitored operational contact and agree on escalation paths for urgent fraud, service incidents, and cases that require your input.
2. Confirm any private channels or recurring meetings included in your service scope. Unbranded support doesn’t include custom platform operations channels by default.

## Prepare agent training and communications

Stripe trains agents on supported product workflows, authentication, privacy, disputes, and complaints. The preparation you provide depends on your support model.

### Branded 

Provide a program overview, customer-facing application access, escalation paths, and the factual information agents need to support your program. Review and approve IVR scripts, email templates, canned responses, the question bank, and operating procedures with your product, legal, and marketing teams as appropriate.

Include rewards or other platform context in training where it helps agents recognize an out-of-scope question. Training material doesn’t expand the agreed upon support scope.

### Unbranded 

Stripe maintains standard product training, IVR scripts, responses, and operating procedures. You don’t need to create platform-specific training or customized scripts. Share integration details that affect standard servicing, your redirect destination, and required disclosures.

## Supply volume forecasts

Provide expected active users and contact volume for the next 3 months, and update the forecast monthly. Notify Stripe at least 1 month before marketing campaigns or other events that could increase demand. Stripe uses these forecasts to plan staffing and agent preparation.

## Test and launch

Agree on implementation milestones with Stripe before setting your launch date. Plan for scope definition, technical integration, communication approval, agent training, testing, and launch readiness. Branded customization and migrations add dependencies, including domain configuration and existing-customer data import. Confirm the minimum lead time for your program with your account team instead of assuming support can launch the following week.

Before launching, verify:

- Customers can find the correct support number and required last-four identifiers in your application, card, statement, and help content.
- Caller identification, fallback authentication, and multi-factor authentication work as expected.
- Contact information updates reach Stripe, and migrated customer data is available for authentication.
- Agents have the required access and can complete supported workflows.
- Card dispute API intake, phone intake, complaint routing, evidence submission, and escalation paths work as agreed upon.
- Out-of-scope questions reach a monitored platform support destination.
- Branded IVR, email delivery and replies, regulated notices, and approved communications work where applicable.

Resolve launch-readiness issues with Stripe before enabling the service for customers.
