Customer support

BridgeAD support for active migration work.

BridgeAD support is for active customers and security or legal requests. For demos, assessments, or pricing, use the sales enquiry form. For urgent operational issues affecting an active migration, include [URGENT].

Response expectations

By topic

Sales & pre-sales

Pricing, demonstrations, scoping, and assessment planning.

Open structured sales enquiry

Customer support

Existing customers, in-flight migrations, and configuration support.

support[at]bridgead[dot]in

Security & vulnerability disclosure

Coordinated disclosure, security questionnaires, and pen-test reviews.

security[at]bridgead[dot]in

Privacy & legal

Data-subject requests, DPA requests, and sub-processor information.

privacy[at]bridgead[dot]in · legal[at]bridgead[dot]in

Start an enquiry

Complete the details below to open a support email draft in your preferred mail application. Do not include credentials, tokens, or personal data exports.

Office

Apqor Technologies Pvt Ltd
Rajapushpa Summit, Nanakramguda Road,
Financial District, Hyderabad - 500032,
Telangana, India
General: info[at]bridgead[dot]in

Status & documentation

SaaS service status and incident history are available to customers on request. Deployment guides, architecture notes, and runbooks are also available on request — email support[at]bridgead[dot]in.

What happens after you reach out

Triage

Every enquiry is routed to the specialist matching your topic — migration engineering, security, or commercial — not a generic inbox. Active migration incidents are triaged first during business hours.

Escalation

If an in-flight migration is blocked, say so in your first message and include the job or tenant reference. Blocking issues are escalated to the on-call engineer rather than queued behind general questions.

What to include

Approximate scope, the platforms on each side, any error or job reference, and your cutover or compliance window. This lets the first response be concrete instead of a request for more detail.

What never to send

Never include credentials, access tokens, or personal-data exports in a support message. Connectivity is established later through your own controlled channels.

Book a technical demo Contact support