Contacting support
BuiltForProd support is reached over email, Slack and video conferencing; the offerings note names these three channels for every Managed option. The addresses, workspace and meeting details are given to you when your engagement starts and are not published here. For a purchase or a new engagement, BuiltForProd is reached over email or through its website, or, for AWS products, through a private offer request on AWS Marketplace.
Channels
| Channel | Use it for |
|---|---|
| Anything that needs a record: a new request, a question with attachments, a change of scope | |
| Slack | Day-to-day conversation, quick questions, and incident coordination when you hold Support SLA or Team Augmentation |
| Video conferencing | Working sessions, reviews and incident bridges |
Open every incident in writing, even when you also start a call, so that the request has a timestamp the SLA clocks can run from.
What to include in a request
An engineer can act at once when the request carries the facts the platform already produces. Include:
- Impact and severity. Which stage (sandbox, dev, staging, prod), what users see, since when, and the severity you believe applies.
- Repository and change. The repository name, the pull request or the commit, and whether the change was applied by
apply.ymlor is still at the plan stage. - The workflow run. A link to the GitHub Actions run. For infrastructure runs, attach the run report artifact (
run-report-plan,run-report-apply, with the stage suffix in the blueprint repositories): it lists every unit with its result and reason, which is quicker to read than the log. - The plan or the error. The relevant part of the plan output or the error message, as text, not a screenshot.
- What already changed. Any console action, drift issue or manual step taken during the incident, so that the engineer knows where the environment and the code disagree; see drift.
- Account, subscription or project and region. The name and region, for example
plat-prodandus-west-2on AWS,acme-plat-prodandeastus2on Azure,acme-plat-prodandus-west1on GCP; never credentials.
Never send keys, tokens, private key material or decrypted secrets. Secrets live SOPS-encrypted in the secrets repository and in the stage's secret store (SSM Parameter Store, Key Vault or Secret Manager); an engineer who needs one will use the access your agreement grants.
Where to look before you write
- The drift detection workflow opens an issue labeled
driftwhen a folder's plan is not empty; check the repository's issues first. - The FAQ answers the recurring questions about support options, channels and what support covers.
- The design decisions and upgrade guides in the documentation set of your Baseline edition explain the expected plan output for each change and each upgrade.
Which option you hold decides whether a response window is guaranteed; see support options.