AddisFly - Sub-Agent PCC Setup — Travelport Galileo (1G) for Foreign Partners — SOP
Sub-Agent PCC Setup — Travelport Galileo (1G) for Foreign Partners — SOP
Who this is for: Sales Managers, Booking Admins, and the CEO office (for signing). What it covers: giving a foreign travel company (e.g. a China / Hong Kong partner) their own dedicated Galileo (1G) PCC so they can be set up to ticket through Addis Fly — from agreement to PCC live.
Done before: GuangDong QIYOUJI (China) and Hong Kong NG Chow (Hong Kong). This SOP turns that into a repeatable process.
Key facts (the constants — do not change)
| Item | Value |
|---|---|
| Who we send the request to | Ibsa Negasa, Travelport Ethiopia (Ethiopian Airlines) — [email protected] |
| Always Cc | [email protected] |
| Send from | [email protected] (CEO) |
| Our consolidator | Addis Fly · PCC 593Y · Travelport MCN 670923 · POS Ethiopia |
The stages at a glance
| Stage | What happens | Who |
|---|---|---|
| 0. Agree | Partnership agreed; partner supplies their details | Sales |
| 1. Selective Access Agreement | We sign the form authorising 593Y to ticket for them | Sales Manager + CEO |
| 2. 3rd-Party PCC request letter | Prepare the Letter requesting a brand-new 1G PCC | Sales Manager |
| 3. Email Ibsa | Send both documents using the email template | CEO office |
| 4. Receive PCC + CID | Ibsa replies with the assigned PCC and CID | — |
| 5. Record & go live | Save PCC/CID, confirm selective-access binding | Booking Admin |
The two documents (this is what Ibsa needs)
- Selective Access Agreement Form — signed by Addis Fly. Authorises our PCC 593Y to access and ticket PNRs for the partner. Tick the functions to PROVIDE (Booking File Display/Create/Update/Q, Document Production, Private Fares = Y).
- Request to Grant Third-Party 1G PCC Access — a Letter (doctype
Letter, e.g.LET-2026-00084) that asks Travelport to allocate a brand-new, standalone 1G PCC for the partner. It states: Agent A (Consolidator) = Addis Fly (MCN 670923, PCC 593Y); Agent B = the partner; POS Ethiopia; the PCC is brand-new with no history; no incentives to us; charges are the partner's.
Stage 3 — Send the email (use the template)
Open /app/email → Compose → Email Template → "Request to Grant Third-Party 1G PCC Access (Sub-Agent Onboarding)".
Fill the placeholders: [PARTNER COMPANY NAME], [PARTNER CITY, COUNTRY], [LETTER REF].
Attach both PDFs (the signed Selective Access Agreement + the 3rd-party request letter) — templates do not carry attachments, so add them manually. To: Ibsa. Cc: Travelport Ethiopia. Send from [email protected].
Stage 4–5 — When Ibsa replies
Ibsa replies with the new PCC, e.g.:
NAME: ADDISFLY HONG KONG NG · PCC: H6R · CID: GCICV7TG
Record it on the partner's Partner Account:
- Open the Partner Account → GDS & PCC tab → Additional PCC Configurations → add a row: Partner PCC = the new PCC, GDS System = Travelport, mark Is Default.
- There is no CID field, so add the CID (and PCC name) as a comment/note on the Partner Account and the Customer.
- Leave Primary PCC = 593Y — that is our consolidator PCC (this is how QIYOUJI is set up too). The partner's own PCC lives in the Additional PCC Configurations table, not in Primary PCC.
Then confirm the selective-access binding (593Y ⇄ new PCC) is active. Until it is, ticketing is handled by the Addis Fly team on the partner's behalf.
Common mistakes
- ❌ Overwriting Primary PCC (593Y) with the partner's PCC — 593Y is the consolidator; keep it.
- ❌ Sending the email without attaching the two PDFs (the template has no attachments).
- ❌ Forgetting to record the CID — there is no field for it, so it must go in a note or it is lost.
- ❌ Treating the PCC as "live" the moment it is created — the selective-access binding must be confirmed first.
How the AI assistant can help
This page is indexed, so you can ask the AddisFly assistant things like: - "How do I set up a new China partner's PCC?" - "Who do we email for a Travelport third-party PCC and what do we attach?" - "Where do I record a partner's PCC and CID?"