Ask CubiCrew for help

You do not need to diagnose the technology before asking for help. A clear description of the work you wanted and where you got stuck is enough to begin.

Start with any support instructions included in your handoff. The general contact listed in CubiCrew’s existing documentation is support@braidge.ai. This page does not promise a response time or change your service agreement.

Gather the useful details

Use the smallest example that explains the problem:

1. The job: what you were trying to accomplish.
2. The expected result: what you thought would happen.
3. The actual result: what happened instead, including exact error wording if there is any.
4. When it happened: the date, approximate time, and your time zone.
5. The current position: whether work is waiting, a draft exists, or an action already happened.
6. What you tried: one or two checks, and whether this used to work.

If the job is time-sensitive, state the real deadline and the business consequence of missing it. That helps explain the situation; it does not reserve a support response time.

Use this message as a starting point

Make this request your own

Subject: Help with [short description]. I was trying to [job]. I expected [result], but [what happened]. This occurred around [date, time, time zone]. The exact message was [error, if any]. I have already checked [checks]. The work is currently [waiting, draft ready, or action already taken]. My deadline is [deadline, if relevant]. Please help me identify the next step.

Replace every bracketed item before sending. Remove any line that does not apply. A short, complete example is easier to investigate than a long account of every attempt.

Share only what the investigation needs

Keep passwords, sign-in codes, access keys, private customer information, and confidential documents out of the initial email. A screenshot can help if you crop or cover unrelated details. Check the image itself before attaching it.

If support needs private material, ask which approved sharing route to use. A public link to this learning site is safe to share as an explanation. A link to your employee or business files may grant access and needs separate care.

While you wait

Keep the original job and error available. Avoid repeatedly starting the same work or changing several settings at once. If a deadline cannot wait, use your existing business process to complete the work yourself or assign it to a person.

A useful handoff is complete when: support has the intended job, the actual problem, and enough safe detail to identify the next check. Keep any follow-up about the same issue together.