The CRM travel advisors run their book of business out of.
Travel agencies run a motion that looks nothing like a standard sales pipeline. The quote is an itinerary. The buyer is a family with passports, loyalty numbers, dietary notes, and a honeymoon anniversary. The supplier side is a dozen tour operators and cruise lines paying commission on a 90-day lag. The CRM has to hold all of that in one record and surface the right thing at the right time, from the first inquiry email to the airport-arrival text and the one-year rebook nudge.
The travel-agency job is three jobs in a trench coat. Build itineraries that read like a concierge document and price like a tour operator. Keep client profiles so complete the advisor remembers the gluten allergy, the aisle-seat preference, and the kids middle names on the next call. Chase supplier commissions that land 60 to 120 days after the trip while a cruise line restructures its payout file. In most generic CRMs none of those three live in the same record and the advisor spends an hour a day gluing them together. The six pains below show up on every travel-agency buyer call we have run and they are consistent across leisure, corporate, luxury, group, and specialty travel. If any of them look familiar, the rest of the page shows how Strkr collapses the itinerary, the client profile, the supplier ledger, and the post-trip rebook into a single workspace where the advisor finally spends the day on the trips and not on the paperwork.
Client profile scatter
Passport, loyalty, dietary notes live in five places.
The advisor keeps passport scans in a shared drive, loyalty numbers in a spreadsheet, dietary notes in an email thread, and anniversary dates in a desk notebook. The next trip starts with 20 minutes of profile rebuilding. Strkr puts every field (passport number, expiry, nationality, Known Traveler Number, loyalty tier by program, allergies, seat preference, mobility notes, kids ages, home airport, anniversary) on one client record with field-level encryption and expiry alerts for the passport.
Itinerary spaghetti
The itinerary lives in a Word doc that was emailed six times.
The advisor builds an itinerary in Word, prices it in a spreadsheet, emails version 3 to the client, the client replies with a change, version 4 goes out, and nobody is sure which version is live. Strkr itinerary workspaces hold segments, suppliers, pricing, and client-facing branded output on one record with version history and a single shareable link that always serves the current version.
Supplier commission chaos
I booked the trip 90 days ago and still have no payout.
Commission from a tour operator or cruise line lands 60 to 120 days after travel. The advisor tracks expected commissions in a spreadsheet, chases unpaid ones monthly, and never catches the one that paid out at the wrong rate. Strkr supplier records carry commission terms, expected payout date, actual payout, variance alert, and a chase workflow so the advisor sees the ten commissions worth chasing this week on one view.
Departure day missed
The client flew out and I forgot the bon-voyage touch.
The high-touch advisor sends a bon-voyage note the day before departure, an arrival-day check-in text, and a mid-trip concern-check. In practice, these fall through the cracks because the trip is booked and the advisor moves on to the next quote. Strkr fires time-based automations off the departure date on every booking so the touches run on schedule without a mental tickler file.
Rebook window missed
The one-year anniversary of the trip passes without the rebook nudge.
Repeat travelers are the margin of a travel agency. The advisor knows the family goes to Hawaii every February, the couple cruises every October, the corporate account books Vegas every quarter. In practice the rebook window passes because the advisor is heads-down on this week book of business. Strkr fires a rebook flow 60 and 30 days before the anniversary of the last departure, so the nudge goes out when the client is still in planning mode.
Group booking math
A 40-pax group destroys my spreadsheets.
A church group, destination wedding, or corporate incentive is 40 travelers with 23 room configurations, 12 flight preferences, 7 dietary variations, and three payment plans. The spreadsheet collapses under the weight. Strkr group bookings hold per-traveler profiles, room assignments, pre-payment schedules, and consolidated supplier bookings on one project-shaped record so the group lead sees the whole picture without rebuilding the sheet.
Document retention
I need the signed waiver and I cannot find it.
Travel-insurance declination forms, group waivers, honeymoon-specific terms, visa documents, and vaccination records are mandatory for some trips and critical for post-trip disputes. Half the time the signed form is in an email somewhere. Strkr stores signed documents on the booking record with DocuSign and PandaDoc integrations driving the signature, and the retention timer tracks required hold periods for the destination compliance regime.
How Strkr fits the travel-agency day
The daily primitives travel advisors actually use.
Strkr for travel agencies is not a different product than Strkr for consulting firms or SaaS teams. It is the same CRM with industry-shaped records, flows, and views that make the travel-advisor day cleaner. Everything below ships on every paid tier with no premium module gate or add-on charge. The primitives are shaped around what a travel advisor repeats every week: triaging new inquiries, building and pricing itineraries, booking across supplier systems, running departure-day touches, and chasing the commission file 90 days later. When those five motions happen in one workspace with one record of truth per client, the advisor finally spends the day on the trips and the clients, not the paperwork and the spreadsheets.
Client profile
One record holds the whole traveler.
The client record holds passport number and expiry, nationality, Known Traveler Number, Global Entry status, loyalty program and tier for every program they carry, allergies, seat and bed preferences, mobility notes, dietary restrictions, home airport, anniversary date, kids names and ages, past trips, and preferred advisor. Sensitive fields encrypt at rest with field-level permissions so the agency owner, not every advisor, controls who sees passport data.
Itinerary workspace
A workspace per trip, segments and supplier on one record.
Every trip is an itinerary workspace with air, hotel, car, cruise, rail, tour, transfer, and activity segments. Each segment carries supplier, confirmation number, cost, markup, retail, commission expected, and status. The client-facing branded output renders from the same data so the advisor never maintains two copies. A single share link always serves the current version to the client.
Supplier directory
Every tour operator, cruise line, and DMC on one record.
The supplier directory holds commission terms, payout schedule, preferred-partner status, host-agency override rules, contact name and phone, net-rate agreements, and the booking policy. When an itinerary pulls a supplier onto a segment, the commission math auto-computes against the supplier record and the expected-payout date lands on the agency commission ledger.
Inquiry triage
Every new lead on a board, routed to the right advisor.
Website quote forms, inbound emails, and phone call logs land on an inquiry board. The flow routes to the advisor who owns the client, or round-robins across available advisors by specialty (Europe, cruise, luxury, family, corporate). The advisor sees the full inquiry context (destination, dates, pax, budget band, past trips) on the first card so the first reply is a real reply, not a please-tell-me-more reply.
Departure queue
Today departures and arrivals on one view.
A departure queue surfaces every booking departing today, tomorrow, and the next seven days with pre-departure checklist status, outstanding documents, and the last touch sent. The advisor runs a 10-minute morning pass over the queue, confirms the bon-voyage touches went out, and spots the one booking that still needs the final hotel voucher before the client lands.
Commission ledger
Every expected and received commission on one surface.
The commission ledger lists every booking with expected commission, expected payout date, actual payout, variance, and chase status. Overdue payouts flag automatically. Variance alerts fire when the paid amount differs from the expected by more than the tolerance the agency sets per supplier. The month-end reconciliation that used to be a two-day spreadsheet session becomes a filtered view with one-click chase tasks.
Mobile for the airport run
Edit the booking from the terminal.
Strkr mobile is first-class with offline queue, voice-note capture, booking edit, and SMS to the client. The advisor at an airport dealing with a client flight cancellation opens the booking on the phone, logs the rebook on the next flight, drops a voice-note next-step, and texts the client the new confirmation code. Everything syncs when the connection returns.
The itinerary buyers actually read
Itinerary tooling built for the advisor and the traveler.
The itinerary is the artifact the client judges the advisor on. Most CRMs treat it as a file attachment and leave the design, pricing, and version control to Word and Excel. Strkr itinerary workspaces hold the segments, pricing, suppliers, and client-facing branded output on one record. The advisor builds the trip once, prices it with real-time supplier math, and the shareable link always serves the current version to the client with a branded render that looks like a concierge document, not a spreadsheet export. The six pieces below are what shows up in every leisure, corporate, and luxury travel configuration we have seen.
Every segment type is a native primitive with the right fields. An air segment carries carrier, flight number, cabin, seat, Known Traveler Number, meal preference, status. A hotel segment carries check-in and out, room type, bed configuration, nightly rate, taxes, cancellation window. The advisor builds a seven-city European tour by stacking 24 segments and the workspace handles the sequence without a sidebar app.
Pricing math
Net, markup, retail, commission on every segment.
Each segment carries net rate from the supplier, agency markup (percentage or dollar), retail price to the client, and expected commission. The itinerary total rolls up the retail for the client-facing view and the commission for the agency ledger. Mixed-currency itineraries convert at the lock rate the advisor set on the quote and recalculate when the lock expires.
Branded render
The client sees a concierge document, not a spreadsheet.
The client-facing render is a branded itinerary with the agency logo, advisor contact, segment-by-segment layout, maps, hotel descriptions, local tips, and emergency contact. The advisor edits a tip or swaps a segment, the shared link updates. The client prints, shares with family, saves to Apple Wallet or Google Wallet, and reads it on the plane without a login.
Version history
Every change tracked, the live version always current.
Every change on the itinerary logs who, what, and when. The advisor sees the full history, rolls back a change, or compares two versions. The client always sees the live version at the shared link, so the moment-of-truth question (which version did we agree on?) is settled by the record and not by a scroll through a long email thread.
Approval and signature
E-sign the booking terms right off the itinerary.
DocuSign and PandaDoc integrations drive the signature on booking terms, travel-insurance declination, cancellation policy, and group waivers. The signed document stores on the booking with the signature audit trail intact for the post-trip dispute scenario. The advisor never asks the client to print, sign, scan, and email the form.
Payment schedule
Deposit, interim, final payments tracked on the booking.
The payment schedule on the itinerary holds the deposit amount and due date, interim milestones, final payment due date, and the client payment status against each. Stripe and other processor integrations capture the payment, mark the milestone paid, and fire a flow to confirm the booking with the supplier when the final payment lands.
The supplier commission motion
Supplier records and the commission chase that actually gets paid.
Supplier commission is where many travel agencies quietly leak money. A cruise line pays commission 90 days post-sail at a tier rate that depends on the agency annual volume. A tour operator pays 60 days post-travel at a flat rate that the host agency overrides on preferred-partner bookings. The agency owner is the only person who tracks every rule in their head, and the moment they step away for a vacation the whole thing starts leaking. Strkr makes the supplier record the single place these rules live, so the commission math happens inside the record and the chase surfaces as a view the junior staffer can run.
Supplier record
Commission terms live on the supplier, not in the owner head.
Each supplier record carries base commission rate, tier breakpoints (if applicable), payout schedule (post-travel vs post-sail vs post-deposit), host-agency override rules, preferred-partner bonus, and the booking policy. The itinerary pulling the supplier onto a segment pulls the rate and schedule, so the expected commission is auto-computed on every booking.
Expected payout
Every booking carries an expected-payout date.
When the booking confirms, the flow computes the expected-payout date from the supplier rule and the departure or sail date. The commission ledger shows every booking with the expected date, so the agency knows the January payout from the September Caribbean cruises is coming in week three and the February payout from the fall European tours is coming in week one.
Variance alerts
A payout that misses the expected rate flags itself.
When the actual payout file arrives (ARC statement, cruise line file, tour operator payout) and the number differs from the expected by more than the tolerance, Strkr flags the variance on the ledger. The advisor opens the booking, sees the difference, and runs the chase without discovering the leak three months later during month-end.
Chase workflow
Overdue commissions surface and route to a chase task.
A commission 15 days past the expected date surfaces on the chase queue. A one-click chase task fires the templated email to the supplier accounts receivable with the booking reference, expected amount, and travel date. The chase cadence runs on a schedule, so the junior staffer runs the ten chases this week without the owner holding the mental tickler file.
ARC and consolidator sync
Payout files parse into the ledger.
ARC settlement files, cruise line payout files, and tour operator payout CSVs import into the ledger with a parser the agency sets up once per supplier. The import matches payouts to bookings by confirmation number and marks each paid, flags each variance, and leaves the un-matched rows for the advisor to reconcile. The month-end reconciliation becomes an hour, not a two-day session.
For host agencies and agencies with independent-contractor advisors, Strkr computes the advisor payout off the commission received, the advisor commission split, and any overrides. The monthly advisor-payout report ships from the ledger with no spreadsheet reconciliation. The ICs see their own payout view scoped to their bookings and never see the agency gross.
Flows for the travel-agency motion
Automations that cover the full travel-agency day.
The best travel advisors are not the ones who grind the longest; they are the ones who automate the quiet administrative drag and spend their hours on the trips where judgment matters most. Strkr Flows handle the dozen automations every travel agency should run, and each one ships as a native trigger with no webhook plumbing or glue code. The pattern below is what shows up in week two of every deployment, and it is the pattern that quietly compounds into a cleaner departure queue, less dropped followup, and more rebooks landing on the right 60-day window.
New inquiry
Website quote form fires a routed task to the right advisor.
A quote form submission creates an inquiry record, assigns to the advisor who owns the client (or round-robins by destination specialty), and fires a 15-minute response SLA timer. The advisor sees the inquiry on the board with the full form payload and a draft first-reply template that Strkr AI pre-fills from the destination and the pax count.
Quote sent
Quote to client fires the follow-up cadence.
The advisor sends the itinerary quote to the client. A flow schedules a 48-hour follow-up task, a 7-day warm-nudge email, and a 14-day cold-nudge email with an auto-close at 30 days if the client never responds. The advisor never has to remember the follow-up cadence and never has a quote die of silence.
Booking confirmed
Deposit received fires the supplier confirmation and departure prep.
The deposit payment lands, the flow confirms the booking with the supplier (where supported by API integration), fires a welcome email to the client with the booking summary, creates the departure-prep task list, schedules the pre-departure touches by date, and adds the expected commission to the ledger.
Final payment due
The final-payment reminder goes out on schedule.
Thirty days before the supplier final-payment deadline, the flow emails the client the final-payment reminder with the amount, due date, and payment link. If the payment lands on time, the flow confirms. If it slips, the flow escalates to the advisor so a phone call lands before the supplier auto-cancels the booking.
Seven days before departure the flow fires a document-package email with vouchers, visa reminders, and local tips. One day before departure the flow fires the bon-voyage note. The day after arrival the flow fires an arrival-day check text. Mid-trip the flow fires a concern-check. The advisor edits any touch inline before it ships or lets the auto-fire run clean.
Return home
Post-trip survey plus photo and testimonial request.
Three days after return, the flow fires a thank-you note, a short survey (Net Promoter plus three open-ended questions), and a soft ask for a photo and testimonial. The responses land on the client record for future reference and the testimonial surfaces to the agency marketing queue for consent-based use.
Rebook window
Sixty and thirty days before trip anniversary.
Sixty days before the anniversary of the client last departure, the flow fires a soft nudge (Thinking of your next trip? Here is what is new). Thirty days before, the flow fires a follow-up with three suggested destinations shaped by the client past-trip history. The advisor sees the responses on the inquiry board and the rebook pipeline fills itself.
Specialty travel configurations
Leisure, corporate, luxury, group, specialty on one platform.
A single agency often runs multiple shapes of business. A leisure advisor on honeymoons and anniversaries. A corporate desk on business travel for a dozen company accounts. A luxury specialist on Virtuoso and Signature bookings. A group lead running destination weddings and corporate incentives. Specialty desks on cruises, safaris, religious travel, or adventure. Strkr handles all of them on the same tenant with pipeline-level configuration, role-based access, and a shared supplier directory, so the agency does not run four different CRMs. The six configurations below are patterns the Strkr team supports in production today.
Leisure
Family vacations, honeymoons, anniversaries.
The leisure pipeline runs inquiry to departure in a motion that favors a quote within 24 hours, a soft follow-up cadence, and a strong pre-departure touch rhythm. Client profiles emphasize anniversary dates, kids ages, and preferred destinations. The rebook flow fires on the anniversary of the last trip. Luxury-brand suppliers (Virtuoso, Signature) carry preferred-partner overrides on the commission math.
Corporate
Business travel for company accounts.
The corporate pipeline treats a company as the account and the travelers as contacts under it. Travel policy fields on the company record (preferred carriers, class of service by employee tier, hotel approved list, car rental vendor) auto-apply to new bookings. Monthly reporting ships to the company travel manager with pre-built templates. GDS integration for GDS-driven corporate agencies is in-scope on the agency Flow configuration.
Luxury
Virtuoso, Signature, FHR, Internova.
The luxury advisor runs a smaller book of bigger trips and a longer discovery cycle. The client record carries preferred-brand loyalty (Four Seasons, Rosewood, Belmond), amenity-program eligibility, and private-aviation preferences. Preferred-partner overrides on the commission math capture the Virtuoso and Signature bonuses that are the margin of the luxury business.
Group
Destination weddings, corporate incentives, church groups.
A group booking is a project-shaped record with per-traveler profiles, room assignments, pre-payment schedules, consolidated supplier bookings, and a group-lead contact. The group workspace holds the master itinerary and the per-traveler variations (triple-share vs double, kid meal vs adult, pre-tour vs post-tour extension). Payment plans run per-traveler against the master commission.
Cruise specialty
Cabin categories, group blocks, cruise line specifics.
The cruise desk works with a different vocabulary (sailing, embarkation, debarkation, group block, cabin category, port fees, drink package). Strkr adds those fields to the cruise segment type without a sidebar app. Cruise-line payout files parse into the ledger natively. The post-sail commission timeline is 60 to 120 days and the chase queue surfaces the ones that are late.
Adventure and specialty
Safari, religious, culinary, expedition cruise.
Specialty travel runs on different suppliers (specialty tour operators, direct DMC relationships) with different commission structures (per-pax, flat per-booking, net-rate with resale). The supplier record flexes to hold the rule, the segment captures the specialty fields (dietary for culinary, land-vs-sea for safari, denomination for religious), and the pipeline runs the same way as the leisure flow with the right field surface on the itinerary.
What the agency owner sees
Views that make the Monday agency review fast.
A good agency owner coaches on three advisors a week, not on all 12 in the roll. Strkr surfaces the data the owner needs to run a short, specific weekly review without the advisor feeling surveilled, because the same views are available to the advisor and the owner with the same filters. The views below ship as default saved views for the owner role on every tenant and can be duplicated and personalised without an admin ticket.
Advisor roll
Each advisor on one row with bookings, revenue, pending.
The Monday review puts every advisor on one row with bookings closed this week, revenue booked, pending inquiries, commissions received, and the number of overdue chases. The owner sees the full roll in one scroll and drills into the specific records behind any cell. Reviewing 12 advisors takes 10 minutes, not an hour.
Top clients
Top 20 by lifetime value with next-trip signal.
A top-clients view sorts by lifetime value with last-trip date, rebook signal strength (Strkr AI reads frequency and past-booking patterns), and advisor ownership. The owner spots the highest-value client with no touch in 90 days and the advisor runs a personal outreach before the client books with somebody else.
Stuck quotes
Quotes aged past the cadence threshold.
The owner stuck-quote saved view surfaces every quote that is past the cadence threshold with no advisor action. One click to assign a coaching task, one click to escalate, one click to clear the flag. The thresholds are tunable per quote type so the honeymoon quote and the quick corporate quote carry different windows.
Departure risk
Bookings departing in 14 days with open items.
A departure-risk view shows every booking departing in the next 14 days with any open item: unsigned waiver, missing final payment, document package not sent, outstanding visa requirement. The owner reviews the list on Monday and the advisor clears the items before the client is at the airport asking for the e-ticket.
Commission attainment
Agency commission pacing versus plan, with supplier split.
Agency commission pacing against the quarterly plan with a split by supplier shows which supplier mix is driving the current pace. The owner spots the cruise line that is 30% off plan and the luxury segment that is 20% ahead, and the Tuesday team meeting runs on the two or three real conversations the data surfaces.
Client-complaint queue
Negative-sentiment surveys and refund requests.
Every post-trip survey with a sub-threshold NPS, every refund request, and every escalation flag lands on the complaint queue. The owner sees them before they turn into chargebacks and the advisor runs the service-recovery outreach while the client is still inside the window to resolve the issue without a dispute.
Head-to-head
Strkr for travel agencies vs ClientBase plus TRAMS plus spreadsheets.
A typical travel agency stack runs ClientBase or TRAMS for the back-office commission file, a quote tool like Travefy or AXUS for the itinerary, Mailchimp for the newsletter, Dropbox for the signed documents, and spreadsheets for the group bookings and the chase queue. Strkr collapses most of that into a single workspace with one bill, one admin surface, and one record of truth for every client, every itinerary, and every supplier.
Feature
Strkr
ClientBase + Travefy + Dropbox + spreadsheets
Number of tools advisor opens daily
1 (Strkr)
4 to 6
Client profile with passport, loyalty, preferences
Native with field-level encryption and expiry alerts
ClientBase client card plus Dropbox for scans plus spreadsheet for loyalty
Itinerary builder with branded output
Native workspace with versioned client-share link
Separate Travefy / AXUS SKU, PDF export
Supplier commission ledger
Native with expected payout, variance alerts, chase workflow
TRAMS reports plus month-end spreadsheet reconciliation
Mailchimp automations manually tied to spreadsheet dates
Rebook flow at trip anniversary
Native flow 60 and 30 days before anniversary
Advisor memory, mental tickler file
Group booking with per-traveler profiles
Native project-shaped record with payment plans
Spreadsheet, lost at 25 travelers
E-signature for waivers and insurance declination
DocuSign and PandaDoc native integrations
Print, sign, scan, email, Dropbox
Independent-contractor advisor payouts
Native computation off commission split and overrides
Monthly spreadsheet reconciliation
Mobile for the airport run
First-class with offline queue and voice notes
Thin wrapper, limited edit, no offline
ARC / cruise line / tour operator payout file parsing
Native parser per supplier, auto-match to bookings
Manual spreadsheet import
Agency owner coaching views
Native advisor roll, stuck quotes, departure risk
Custom report cobbled from TRAMS extracts
How teams use Strkr
How travel agencies run Strkr.
The patterns below show up across travel agencies of 4, 12, and 30 advisors. The common thread: collapse the client record, the itinerary, the supplier ledger, and the departure flow into one surface so the advisor spends time on the trips and not on stitching. Each playbook is a real motion a Strkr-shaped travel agency runs today, not a hypothetical configuration from a demo script.
4-advisor leisure agency
Owner plus three ICs on honeymoons and family vacations.
A four-advisor leisure agency moved off ClientBase and Travefy. The client record held the whole family (passport data for parents, kid ages, dietary notes, home airport, past Hawaii trips). The itinerary workspace shipped branded quotes in half the build time. The rebook flow fired 60 days before the anniversary of every honeymoon and the Caribbean cruise. The agency owner reported the Monday review dropped from two hours to twenty minutes and the rebook rate climbed 18 points over four months.
12-advisor host agency
Luxury plus leisure plus corporate on one tenant.
A 12-advisor host agency ran luxury on Virtuoso bookings, leisure on honeymoons and family, and a corporate desk on three company accounts. The pipeline-level configuration let each desk run its own fields, cadence, and client-facing render without a separate tenant. The commission ledger auto-parsed ARC files and cruise line payout files, and the IC advisor payout reports shipped monthly with zero spreadsheet reconciliation. Supplier chases went from the owner-only task to the junior admin running the ten chases a week on the queue.
30-advisor leisure cooperative
Supplier commission ledger plus group bookings plus rebook flow.
A 30-advisor cooperative with a central back-office ran the commission ledger as the source of truth for all 30 ICs. Expected-payout dates landed on the ledger at booking time and the chase queue surfaced the overdue items weekly. Destination-wedding group bookings held per-traveler profiles with payment plans per attendee. The rebook flow drove 23% of the following-year revenue from the previous-year client base and the owner reported the agency finally scaled past the point where everything used to live in her head.
Specialty cruise agency
Cruise cabin categories plus group blocks plus post-sail commission chase.
A cruise-specialty agency with 8 advisors sold Caribbean, Mediterranean, and Alaska itineraries with group blocks of 20 to 60 cabins. The cruise segment type held cabin category, deck, embarkation, debarkation, drink package, and port fees. Group blocks ran as project-shaped records with payment plans per cabin and the cruise-line payout file auto-parsed into the ledger 90 days post-sail. The variance-alert feature caught a cruise-line rate-table change that would have cost the agency 15 points of margin on the Alaska bookings before anybody noticed.
Corporate travel desk
Policy-driven bookings for a dozen company accounts.
A corporate desk inside a mixed agency ran business travel for 12 company accounts. The company account held travel policy (preferred carriers, class of service by employee tier, hotel approved list) and the policy auto-applied to new bookings. Monthly reporting shipped to each company travel manager with pre-built templates. The GDS integration drove the ticket issuance and the reconciliation of GDS commissions landed on the same ledger as the leisure direct-booked commissions, so the agency owner saw one book not two.
See the CRM travel agencies actually run bookings in.
Start a 14-day trial with the full travel-agency stack enabled: client profiles with passport and loyalty data, itinerary workspaces with branded output, supplier commission ledger with ARC file parsing, pre-departure and rebook flows, group bookings with per-traveler profiles, and DocuSign plus PandaDoc contract integrations. One bill, one workspace, one record of truth for every client, every itinerary, and every supplier. The pricing page lays out the per-seat line in full so there is no mystery before the trial starts, and the integrations page shows the ClientBase migration path if the question is how to move an existing agency book over.
Can Strkr replace ClientBase or TRAMS for a travel agency?
For most agencies under 100 advisors on standard leisure, corporate, luxury, or specialty motions, yes. Strkr covers client profiles with passport and loyalty data, itinerary workspaces with branded output, supplier directory with commission math, payment schedules with Stripe and other processor integrations, pre-departure flows, rebook flows at trip anniversary, group bookings with per-traveler profiles, and the commission ledger with ARC and cruise line payout file parsing. For agencies running GDS-only corporate motions with deeply-customized Sabre or Apollo integrations, the migration is a longer conversation and Strkr has a native migration path for ClientBase extracts that preserves client records, booking history, and commission records.
How does the supplier commission ledger work?
Each supplier record carries commission terms (base rate, tier breakpoints, preferred-partner override, payout schedule post-travel vs post-sail vs post-deposit). When an itinerary pulls a supplier onto a segment, the commission math auto-computes against the supplier record and the expected-payout date lands on the ledger at booking confirmation. Overdue payouts flag on a chase queue and variance alerts fire when the actual payout differs from the expected by more than the tolerance. ARC settlement files, cruise line payout files, and tour operator payout CSVs import into the ledger with a per-supplier parser, matching payouts to bookings by confirmation number and leaving the un-matched rows for the advisor to reconcile.
How does Strkr handle group bookings for destination weddings and corporate incentives?
A group booking is a project-shaped record with the group lead as the primary contact, per-traveler profiles under the group, room assignments, pre-payment schedules per traveler, and consolidated supplier bookings on the master itinerary. The group workspace holds the master itinerary and the per-traveler variations (triple-share vs double, kid meal vs adult, pre-tour vs post-tour extension). Payment plans run per-traveler against the master commission so the agency sees the pacing per attendee and the group lead sees the roster roll. The group document pack (waivers, insurance declinations, visa reminders) runs per-traveler via DocuSign and PandaDoc.
Does Strkr integrate with DocuSign and PandaDoc for travel waivers and insurance declinations?
Yes. Both DocuSign and PandaDoc ship as native integrations. Draft the waiver, travel insurance declination, cancellation policy, or group terms from the booking record, route for signature, and the signed PDF returns to the booking with the signature audit trail intact for the post-trip dispute scenario. The retention timer tracks the required hold periods for destination compliance regimes so the signed documents stay on record for the required window and surface for secure deletion after.
What is the rebook flow and how does it work?
Repeat travelers are the margin of a travel agency and the rebook flow protects the window where the client is most likely to re-book. Sixty days before the anniversary of the client last departure, the flow fires a soft nudge to the advisor outbox with a draft message pre-filled from the client past-trip history. Thirty days before, the flow fires a follow-up with three suggested destinations shaped by the past-trip data. The advisor edits any of the touches inline before they ship or lets the auto-send run clean. Strkr AI pre-fills the three destination suggestions from the client past-trip pattern (Hawaii every February, cruise every October), so the advisor spends the time on the personal note and not on the destination research.
Can independent-contractor advisor payouts be automated?
Yes. For host agencies and agencies with independent-contractor advisors, Strkr computes the advisor payout off the commission received, the advisor commission split (configurable per advisor and per booking type), and any overrides. The monthly advisor-payout report ships from the ledger with no spreadsheet reconciliation. The ICs see their own payout view scoped to their bookings and never see the agency gross. The payout computation handles mixed-currency commissions and the override rules for preferred-partner bonuses and luxury-brand amenity-program fees.
How does Strkr handle passport data, loyalty numbers, and other sensitive client data?
Sensitive fields on the client record (passport number, Known Traveler Number, loyalty program numbers, date of birth) encrypt at rest with field-level permissions so the agency owner, not every advisor, controls who sees passport data. Access to encrypted fields logs to the audit trail. Passport expiry alerts fire 180 and 90 days before the passport expires so the client has time to renew before the next international trip. Compliance with GDPR, PCI-DSS, and SOC 2 is on the Strkr Trust page in detail and the data processing agreement covers travel-industry specifics on request.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
We use cookies.
Essential cookies keep the site working. If you accept, we also enable Google Analytics
so we can see which pages help and which don't. Reject to opt out entirely. Details in our
Privacy Policy.
