Account

Support and notifications

Open a case when you need help; the support team answers in the dashboard and by email. Everything you should know about lands under the dashboard's bell.

Cases#

Any member of the team, in any role, and any API key can open a case. Owners and admins see and answer every case of the team; everyone else only the cases they opened.

Field	Value
`category`	`billing`, `account`, `function`, `app`, `database`, `cache`, `storage` or `other`
`severity`	`low`, `normal` (default), `high`; `urgent` on Pro only
`resource`	optional: one of the team's own, e.g. `{"kind": "app", "name": "my-site"}`
`attachments`	optional: up to 3 files, 2 MB each; images, PDF or text
`status`	`open` (waiting on support), `pending` (waiting on you) or `closed`; your reply opens a closed case again

cloudhost support open "Deploys fail since this morning" --category function --severity high \
  --resource function:my-api --file build.log --message "Every deploy fails at the build step."
cloudhost support list --status active
cloudhost support show 12
cloudhost support reply 12 --message "It works now, thanks"
cloudhost support close 12

An AI assistant can do the same with the MCP tools list_support_cases, get_support_case, open_support_case and reply_support_case; closing a case is left to you.

Support's answers#

When support answers, whoever opened the case gets a notification and an email (as their notification settings say).
The support team's internal notes are never shown to you.
Everything the support team does on your case (a reply, an assignment, a status change) is in the team's activity log as staff:<email>.

Notifications#

Event	Who
`deploy_failed` · `build_failed`	owners, admins and developers; a failed production deployment or preview build
`alert_fired`	owners, admins and developers; its email and SMS come from the alert rule itself
`budget_80` · `budget_100` · `wallet_low`	owners and billing members; their email and SMS are sent separately
`invoice_issued`	owners, admins and billing members
`member_invited` · `member_joined`	owners and admins
`support_reply`	whoever opened the case

Each person chooses, per event, whether it goes to the notification centre, email or SMS: in the dashboard under Settings, Notifications, or with PUT /v1/me/notification-settings. Notifications belong to a person, so these routes need a dashboard session; API keys are refused.

Example

curl -X PUT -H "Authorization: Bearer $SESSION" \
  -d '{"events":[{"type":"support_reply","sms":true},{"type":"build_failed","email":true}]}' \
  https://api.ibel.ai/v1/me/notification-settings