> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stackshift.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# Offer a customer support portal

> Let customers read help articles, submit requests and follow their own conversations.

<Note>
  This guide includes features awaiting release. If an option is not available in your workspace, contact StackShift Support.
</Note>

## What you can do

Let customers read help articles, submit requests and follow their own conversations. Where to find it: Settings → Portal operations; your published portal

## Before you start

* A brand, configured portal and an inbox to receive requests.
* A published customer request form if you want structured ticket intake.

## Steps

<Steps>
  <Step>
    Configure the portal for the correct brand and environment in Portal operations.
  </Step>

  <Step>
    Review its appearance, enabled customer forms and the inbox receiving requests.
  </Step>

  <Step>
    If using your own domain, follow the domain verification instructions displayed for that portal. Ask the person who manages your domain to add the exact DNS record; wait for verification and certificate readiness.
  </Step>

  <Step>
    Open the portal as a customer. Browse public knowledge, sign in through the offered verification flow and submit a test request.
  </Step>

  <Step>
    Confirm the request reaches your staff and that the customer can view its reply. Share the ready portal address with customers.
  </Step>
</Steps>

## Example

Link Help from your website to the portal so customers can first search answers, then contact your team.

## Things to know

* A staff account and a customer portal session serve different purposes.
* Customers do not gain access to other customers’ tickets merely by sharing an email domain.
* Changing DNS can require your domain administrator; no programming is needed for that record change.

## What happens next

<Check>
  Customers have a destination for self-service and for tracking requests they are authorized to see.
</Check>

## If something goes wrong

<Warning>
  * Portal unavailable: check brand/environment configuration and domain status.
  * Cannot submit: check customer sign-in, required form fields and whether the form is published.
</Warning>

## Related guides

<CardGroup cols={2}>
  <Card title="Create customer request forms" href="/stackshift-support/ticket-forms">
    Collect the details staff need before a structured request reaches the team.
  </Card>

  <Card title="Create and organize your help centre" href="/stackshift-support/knowledge-centre">
    Give customers a searchable place to find answers before contacting your team.
  </Card>

  <Card title="Run a customer community" href="/stackshift-support/community">
    Let customers discuss topics, share answers and report inappropriate content.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.