airTRFX Delivery
What to expect before, during, and after launching airTRFX
During the Delivery our main goal is to achieve a predictable, uninterrupted, fast launch of airTRFX. We provide training on airTRFX Control while setting up your airTRFX System and we work with the “airTRFX User Experts” on your team. We inform customers regularly with executive status updates.
After the airTRFX delivery we manage ongoing channel adoption and provide strategic advice and best practices for all channels. All customers receive quarterly business reviews and ongoing executive communication. For any and all needs, we provide 24/7 product support via Help Desk.
EveryMundo teams throughout the Product Lifecycle
We are with you every step of the way throughout the implementation process and beyond. Learn more about working with EveryMundo.
Product Delivery Timeline
airTRFX is prepared and deployed in 8 phases in as little as 18 weeks. Below find the topics covered in each phase as well as the estimated effort required by customer team members.
Phase 1: Pre-Kick-off Welcome Package
Key Discussion Topics:
- Welcome Package review
- Deep-link requirements
- Airports source requirements
- Flight Search Panel business rules
- Airline brand guidelines
- FareNet: Airline fare logic
Deliverables:
Customer:
- Completion of all steps in EveryMundo’s Welcome Package including: Deep-link documentation, airports source documentation, Flight Search Panel business rules and airline brand guidelines
EveryMundo:
- Review all questionnaires and documentation submitted by the customer via EveryMundo’s Welcome Package
Teams Involved:
- Customer: Project Manager
- EveryMundo: Product Delivery
Phase 2: EveryMundo Platform Integration
Key Discussion Topics:
- Design guidelines: EveryMundo Design System (EDS)
- FareNet pixel development
- Hosting: Subdomain vs Subdirectory
Deliverables:
Customer:
- Subdomain or Subdirectory implementation
- Implementation of FareNet pixel
- Approval of EDS token values and airline logos
EveryMundo:
- Proposal of EDS token values personalized to airline brand
- FareNet pixel
- CNAME domain or Reverse Proxy Rules with Header Token
Teams Involved:
Customer:
- Project Manager
- Booking Engine Expert
- Pricing Expert
- IBE Tracking Expert
- UX/UI or Design Expert
- Systems Engineer
EveryMundo: Product Delivery
Phase 3: Tracking Requirements
Key Discussion Topics:
- airTRFX dataLayer
- Product tracking requirements
- Site editions and routes
Deliverables:
Customer:
- Submit tracking requirements
- Approve site edition setup
- Grant access to Web Analytics platform
EveryMundo:
- Site edition settings overview
- Routes
- airTRFX dataLayer template
Teams Involved:
Customer:
- Project Manager
- Tracking/Web Analytics Expert
EveryMundo:
- Product Delivery
- Data Analytics
Phase 4: Product Definition
Key Discussion Topics:
- Product definition and configuration
Deliverables:
Customer:
- Approval of Product Definition Form
EveryMundo:
- Delivery of Product Definition Form
Teams Involved:
Customer:
- Project Manager
- Product Owner
EveryMundo:
- Product Delivery
- Customer Success
Phase 5: Training & Airline Content
Key Discussion Topics:
- airTRFX Control training for product configuration
- Geography names audit
- SEO Roadmap Overview
- URL slugs audit
- Location images
Deliverables:
Customer:
- Upload approved metadata and airModules titles
- Upload location content and images (if applicable)
- Approve geography names and URL slugs
- Upload location images in airTRFX Control
EveryMundo:
- Perform airTRFX Control training (Basic functionalities for setup)
- Deliver and present airTRFX SEO Roadmap and Best Practices
Teams Involved:
Customer:
- Project Manager
- Content Team
- Product Users / Web Publishing
EveryMundo:
- Product Delivery
- Customer Success
- Performance Marketing
Phase 6: User Acceptance Testing (UAT)
Key Discussion Topics:
- User Acceptance Testing (UAT)
- Classify feedback as pre-delivery, post-delivery or non-applicable
Deliverables:
Customer:
- Submit UAT feedback via Product Support Desk
EveryMundo:
- Deliver fully-functioning development environment
- Walk-through of product and product test cases
- Grant access to Product Support Desk
- Feedback classification, processing and implementation
Teams Involved:
Customer:
- Project Manager
- Internal QA Teams (if applicable)
EveryMundo:
- Product Delivery
Phase 7: Product Delivery and Marketing Training
Key Discussion Topics:
- Final product review before production release
- Define test transactions methodology
- Review interlinking and redirection plan
- airTRFX Control training for marketing strategies
- Fare Marketing best practices
Deliverables:
Customer:
- Deploy interlinking
- Execute test transactions and verify proper attribution in Web Analytics platform
- Production release to subdirectory/subdomain
- Sign Product Delivery Form
EveryMundo:
- Fully-functioning production environment including UAT feedback classified as pre-delivery
- airTRFX Control training and Fare Marketing best practices
Teams Involved:
Customer:
- Project Manager
- Tracking/Web Analytics Expert
- Digital Marketing team
- Systems Engineer
- Product Owner
EveryMundo:
- Product Delivery
- Customer Success
- Performance Marketing
- Data Analytics
Phase 8: Indexing
Key Discussion Topics:
- Review robots.txt file
- Setup of Google Search Console (GSC)
- Sitemaps generation and submission
Deliverables:
Customer:
- Grant access to Google Search Console
- Finalize Google Search Console properties
- Implement 301 redirects (if applicable)
EveryMundo:
- Assistance with Google Search Console (GSC) setup
- Sitemaps generation and submission
Teams Involved:
Customer:
- Project Manager
- Digital Marketing team
- Web Publishing team
EveryMundo:
- Product Delivery
- Customer Success
- Performance Marketing
airTRFX Control Training Program
The program includes 4 sessions in a total of 4.5 hours, previously completed the online courses on training.everymundo.com corresponding to each session.
Session 1
Completed when pages are ready in Development, but not ready for final UAT
Topics:
- airTRFX Overview (templates and airModules)
- airTRFX Control Overview
- airTRFX Initial Configuration (Routes, Images, Page Contents)
Length: 1 hour
Session 2
Completed when pages are ready in Development, but not yet delivered for UAT
(Session 1 and 2 can happen in the same week)
Topics:
- airTRFX Additional Configuration ( Metadata, Location Images, Content, Labels)
Length: 1 hour
Session 3
Held once UAT has been completed and the product is ready for Production or has been moved to Production
Topics:
- Custom Pages and Custom Fare airModules: Strategic Routes and Promotions
Length: 1.5 hours
Session 4
This training takes place one week after Session 3 has been conducted
Topics:
- Campaigns for Template Pages
- Advanced Assets
Length: 1 hour
Ongoing Support
During the Delivery Process:
- EveryMundo team members will be available via Zoom conference for 60-minutes once per week during the implementation calls.
- For emergencies, EveryMundo team members can schedule phone calls besides the weekly implementation calls.
- Communication outside of the weekly implementation calls should be documented via Basecamp.
- Basecamp is a project management tool which allows both customer and EveryMundo invitees to document requirements, questions and/or clarifications, and decisions made throughout the product delivery process.
Support available post-delivery:
24/7 Product support:
- Report bugs or submit change requests
- Request accesses to airTRFX Control
- Suggest changes
- airTRFX Control or Product Configuration related questions (How to…)
Customer Success Specialists:
- Schedule calls with Customer Success team as needed to discuss product usage roadmap and track progress, ask questions related to strategic usage of product, and general discussions
- Will respond to Basecamp messages within 48 hours
- Other teams will be involved as needed
Development Sprints:
- EveryMundo uses Agile project management methods, including 2-week development sprints which typically start and end on Thursdays.
- Development typically occurs during the first six days of the sprint, followed by QA in each environment (development, pre-production/staging, production).
- Requirements gathering and tickets prioritization occurs 7 days prior initiation of a new Sprint. Any requests or non-critical bugs submitted after the requirements gathering closing window, will not be considered in the immediate upcoming Sprint and will be prioritized for subsequent Sprints.
- In the case of a critical issue, a critical deployment can be pushed outside of the regular sprint schedule.
Ready to launch your Fare Marketing System?
We’ll show you how.