Search Engine: Elastic

Article ID: 6946, created on Nov 26, 2009, last review on Aug 14, 2018

  • Applies to:
  • Operations Automation
  • Business Automation 6.0
  • Odin Business Automation Standard
  • Service provider products licensing


A support code is a 10-digit number divided into 5-character blocks: xxxxx-xxxxx.

The support code is provided by a Sales Representative after you sign a support contract with CloudBlue.

If you have a support code, you need to indicate it while submitting requests to the Technical Support team via email, phone or chat. No matter what way of contacting Support you choose, there will be a step when you will be asked to enter the code.

You can obtain a support code from your Sales Representative or find it in to your RT Self-Service account:

Self Service enables you to track, resolve, create new tickets and re-open the tickets opened on behalf of your company.

If you have never logged in to your Self-Service account before, follow this link to activate your account. You should enter the email address used to contact CloudBlue Support and your ticket number.

A ticket is your request with CloudBlue Support, it is always displayed in the subject of an email sent by CloudBlue Support and looks like this: #1234567. If you contact CloudBlue Support over the phone, the ticket number is given to you before you are connected to a Support representative.

Once your account is activated, you will receive an email with your activation link to the RT Self-Service. .

Complete instructions on activation of the account are available in this article.

NOTE : The incident will be deducted only when a customer opens ticket using the Support Code. If the ticket is created and closed with the Customer Support team, the ticket will not be deducted from the Support Contract.

5356b422f65bdad1c3e9edca5d74a1ae 8fc71f07abe5b233fea1ae0377cd5e3d 0fb3394a2c69b44bea0b259a86272ad9 198398b282069eaf2d94a6af87dcb3ff 3627d36199b8ff577605df76e2fa222b bb7e9177fb03488961a3ea554120f328 400e18f6ede9f8be5575a475d2d6b0a6 3ef1f5f998c0dc182718a7fe4376f875

Email subscription for changes to this article
Save as PDF