Contacts and support
This page describes the contact channels available during integration and what to expect from each.
Customer Success: first point of contact
The first contact for any integrator is the GipoNext Customer Success (CS) team. CS manages the relationship with the medical centre, coordinates onboarding, and routes requests to the appropriate channels.
For contractual, timing, or medical-centre involvement questions, contact CS.
Technical support
For technical integration questions — OAuth configuration, endpoint behaviour, unexpected errors — please submit a ticket into
https://gipo.atlassian.net/servicedesk/customer/portal/140
💡 When to write
Use this channel for specific issues: an error you cannot interpret, behaviour that does not match the documentation, or a question about a specific flow. The more focused the request, the faster the response.
What to expect from support
Technical support is intended for the initial phases of integration: accreditation, first tests, documentation clarifications. It is not ongoing development support.
In practice:
| Support does | Support does not |
|---|---|
| Answers questions about documentation and endpoints | Write code for the integrator |
| Helps diagnose specific API errors | Debug the integrator's application |
| Clarifies OAuth flows and scope configuration | Design integration architecture |
| Reports known issues or maintenance | Provide 24/7 support or guaranteed SLAs |
ℹ️ Responsibility
The integration project — development, testing, maintenance — remains entirely the integrator's responsibility. GipoNext support acts as a facilitator, not as an active development partner.
Next steps
- Getting started — integration path overview
- Accreditation process — how to obtain accounts and credentials
- FAQ — quick answers to common questions