Skip to content
NP4
For TMCs, business travel platforms and other travel service providers.

Itineraries and communications for your clients.

TD doc helps TMCs, business travel platforms and other travel providers deliver itineraries and travel documents from existing booking information. Adapt layouts, logos, service contacts and content to your service or each corporate client. Manage multiple clients in a multi-tenant or jointly managed setup.

Situation

Current itineraries. Consistent communications.

TMCs, business travel platforms and other travel providers manage bookings and changes in their existing systems. Travellers need a clear itinerary: what is booked, when does each service begin and who can help? TD doc combines the travel information supplied with agreed templates and supporting content. A travel provider can serve multiple corporate clients with an individual identity for each, without moving booking and servicing into another system.

How it connects
Current itinerary
Centrally maintained content
TD doc
Itineraries & travel documents
Conceptual flow. Sources and hand-offs are agreed for the specific setup.

Bring the itinerary and content together.

Turn information from connected booking sources into a clear itinerary.

Add company and destination guidance where travellers need it.

Keep branding, contact details and content consistent across email and printable itineraries.

NP4

TD doc complements the existing systems.

NP4 complements existing booking and servicing systems. TMCs, business travel platforms and other travel providers can use TD doc for their corporate clients in a multi-tenant or jointly managed setup, with individual layouts, branding and text for each client.

Approach

From a clear scope to dependable operations.

  1. Define sources & purpose

    Identify booking sources, available data and the document needed: for example, an itinerary, travel offer or cancellation confirmation.

  2. Define clients & templates

    Agree on a multi-tenant or jointly managed setup. Define each client’s logo, colours, layout and text blocks, with appropriate places for travel data and supporting information.

  3. Define delivery

    Agree on recipients, output formats and how new booking versions are handled. Separate responsibility for travel data from responsibility for editorial content.

  4. Validate with examples

    Work through representative trips and changes. Check smartphone presentation, PDF output, links and company guidance together.

Itineraries & documents

The right information in the right place.

An itinerary needs more than booking codes. TD doc presents times, booking references and available service details clearly. Supporting information such as check-in links, baggage allowances or hotel addresses can add the content selected for the trip and the company.

Individual brand identity

Logos, colours, layouts, service contacts and text blocks can be adapted to your service or each corporate client. This gives the travel information supplied the appropriate presentation.

Serve multiple clients

TMCs, travel platforms and other travel providers can use TD doc for multiple corporate clients. Shared content and client-specific adaptations can be maintained in a multi-tenant or jointly managed setup; ownership and approvals are defined during setup.

Mobile & print

Responsive HTML emails and PDF attachments designed for printing serve different purposes. Content and design are adapted for these outputs rather than simply shrinking a screen view.

The additional details shown depend on the available sources and the agreed template.

Operational responsibilities

Keep booking versions, templates and ownership clear.

When a trip changes, the data supplied and the traveller communication need to agree. The setup therefore defines which booking version is used and when an updated document should be delivered. Changes to the booking itself remain part of the existing booking and servicing process.

  • Select document types and delivery channels around actual service needs.
  • Define client-specific templates and clear ownership of content maintained in a multi-tenant or jointly managed setup.
  • Use representative trips with multiple services, changes and cancellations for acceptance testing.
  • Define supporting content and its maintenance with the travel provider and the client company.
FAQ

Implementation questions

Does TD doc replace booking or servicing systems?

No. TD doc complements existing systems with itineraries, travel documents and branded traveller communications.

Which documents and formats can be considered?

The use cases include itineraries, travel offers, ticket receipts and cancellation confirmations. HTML emails and PDF attachments are designed for the agreed document type; the exact scope is defined during setup.

Can we use TD doc for all our clients with individual layouts?

Yes. TMCs, business travel platforms and other travel providers can use TD doc for their clients in a multi-tenant or jointly managed setup. Each client can have individual layouts, logos, colours, service contacts and text blocks. Ownership and approval of client-specific and shared content, along with the language versions needed, are defined during setup.

How are changes to a trip handled?

The booking version supplied by the connected source is the starting point. Triggers and timing for an updated output are agreed and tested with change scenarios. TD doc does not make the booking change itself.

What should we bring to an initial discussion?

An anonymised sample itinerary, the booking sources used, branding requirements and the document types you need are helpful. These make it possible to discuss data gaps, supporting content and delivery in concrete terms.

Privacy · Cookies

Your privacy on np4.net

Necessary cookies keep this website running. Optional analytics, marketing or social-media trackers are not currently embedded. Your choice is stored for 6 months.

Refreshing content in the background