Skip to navigation

Create a Support Request

A support request (or ticket) is a message to IBEE’s support team that is tracked from the moment you send it until the problem is solved. You fill in a short form in the portal; the team replies by email and in the portal, and you keep the whole conversation in one place.

Choose the right form

Your problemFormWhat it asks
A resource, the portal, sign-in or the APITechnicalThe product or portal area, the resource, the issue type, how it affects you, a description
An invoice, a payment, credits or a chargeBillingThe topic, the invoice or wallet record, a description
Pricing, a demo, more capacity or a plan changeSalesA description of what you need

How it works

  1. You open the Support Center and pick Technical, Billing or Sales.
  2. You fill in the form and click Submit Request.
  3. The request gets an 8-digit number such as #07248819, you get a confirmation email, and the portal opens the request.
  4. The team replies; you answer until it’s Resolved.

Before you begin

  • Role: the Owner, an Admin or a Technical member. Collaborators and Billing members don’t see Support; they can email support@ibee.ai. See Team members & access roles.
  • The resource’s name, if the problem is about one VM, bucket or volume.
  • The exact error text, and when the problem started.
  • Screenshots as PNG, JPG, GIF or WebP images, each under 5 MB.
  • Leave out passwords, API tokens and keys.

Create a Technical request

1

Open Technical support

In the portal’s top bar, click Support, then Technical.

2

Choose the product

In Product or portal area, pick what the problem is about. For sign-in, account, organization, portal or API problems, choose Portal & Account. The other choices are Object Storage, Cloud VMs, GPU VMs, Baremetal, Firewall, Block Storage, Container Registry, Email Service, CDN, Secret Manager, VPC, Reserved IPs, Backups, Snapshots, ISOs and SSH Keys.

3

Choose the resource

A second list shows your resources of that type, for example your Cloud VMs, each with its site, status and public IP. Type to search. Choose Other… if it isn’t listed. For Baremetal, type the server’s name in Server.

4

Choose the issue type

Pick the closest Issue Type, for example, for Cloud VMs: Provisioning Failed / Instance Not Created, VM Not Reachable (SSH / RDP), Performance Low / High CPU Usage, Unexpected Reboot / Crash or Resize / Upgrade Request. Questions for that issue type appear underneath; answer each one.

5

Say how it affects you

Under How is this affecting you?, choose one:

  • Question or guidance: how-to, configuration or a general question.
  • Something isn’t working: a problem, but there is a workaround for now. (Selected by default.)
  • Production is impaired: a live service is slow, degraded or partly unavailable.
  • Production is down: a live service is unavailable and there is no workaround.
6

Describe the problem

In Describe the issue or request, write at least 20 characters: what happened, when, what you expected, and any error text. If your resource has no location, you can also pick the Region / Site: Amaravati, IN, Hyderabad, IN, Ashburn, US (the Virginia location, IAD) or Auto.

7

Add screenshots

Under Screenshots (optional), drop images or click to choose them. Keep each under 5 MB: larger files show Failed and must be removed before you submit.

8

Submit

Click Submit Request. The portal shows “Support request created successfully!” and opens your new request.

Billing and Sales requests follow the same pattern from Support → Billing or Support → Sales. They don’t ask how the problem affects you, and Billing asks you to pick the invoice or wallet record it is about.

Follow a request

Click Support → My Requests. The Requests list opens on the Open tab; switch to Awaiting your reply, Closed or All. Search by subject or request number (Search by subject or request ID), or open Filters for status, priority and time.

Each row shows the Request, the Service · Resource, the Status and when it was Updated. New reply marks a reply you haven’t read.

StatusMeaning
ReceivedIBEE has your request
In progressThe team is working on it
Awaiting your replyThe team needs something from you
ResolvedThe team marked it as solved
ClosedThe request is closed

Verify it worked

Your new request appears at the top of My Requests with status Received or In progress, and a confirmation email arrives with its number in the subject.

Reply to a request

Open the request. The header shows its status, product, resource, number and when it was opened, with Refresh. Your original request, with your answers under Issue Details, is at the top of the conversation.

  1. Click Write a reply… at the bottom (or Reply at the top, when the request is Awaiting your reply).
  2. Type your message and add images if needed.
  3. Click Send Reply. Cancel discards the draft.

You can also answer by replying to the email from support@ibee.ai. If you don’t reply within 48 hours of Awaiting your reply, the request closes by itself; you get a reminder after 24 hours.

Reopen a resolved or closed request

You can’t reply to a Resolved or Closed request until you reopen it. Open it and click Reopen ticket; the portal shows “Ticket reopened — you can reply now.” You can reopen a request for 30 days after it closed. After that, the request shows “This ticket was closed too long ago to reopen.”; click Create a new support ticket.

Limits and timing

Value
Describe the issue or requestAt least 20 characters
Screenshot typesPNG, JPG, JPEG, GIF, WebP
Screenshot sizeUnder 5 MB each (the form says 10 MB, but files over 5 MB fail)
Reminder when awaiting your replyAfter 24 hours
Automatic close when awaiting your replyAfter 48 hours
Reopen window30 days after closing
Request number8 digits

Troubleshooting

You seeWhat it meansWhat to do
Issue Type is greyed out (“Select a VM first”)No resource is chosen yetPick a resource, or Other…
A screenshot tile shows FailedThe file is over 5 MBRemove it, shrink or crop it, and add it again
”An attachment failed to upload. Remove it or add it again before submitting.”A screenshot failedAs above
”Wait for the attachments to finish uploading, then submit again.”Screenshots are still uploadingWait, then click Submit Request
The browser asks for more text in Describe the issue or requestIt’s under 20 charactersAdd detail
Error creating support requestThe request wasn’t savedTry again; if it fails again, email support@ibee.ai
”This ticket is too old to reopen. Please create a new support ticket.”It closed more than 30 days agoClick Create a new support ticket

Tips for a faster answer

  • Pick the exact product and resource: the team starts from them.
  • Choose Production is down only when a live service is down with no workaround.
  • Paste the exact error text, the API x-request-id, or the Reference from Activity logs.
  • Say what changed just before the problem started: a deploy, a firewall rule or a resize.