A creator can make a traveler curious about a destination. An advisor can turn that interest into a usable trip brief. A subagent may perform defined work under a supplier account, if the agency and supplier have approved that arrangement. These activities can support one another, but they are not interchangeable roles. Treating them as one informal “partner” relationship creates avoidable confusion around client promises, booking authority, money, and accountability.
Start with the work, then define the role
A content creator may publish destination guidance, bring qualified inquiries, or explain how a trip could fit a traveler’s preferences. That work does not by itself make the creator a travel advisor, a RateHawk affiliate, or an authorized subagent. The creator should identify the nature of the relationship accurately and avoid implying firsthand inspection, supplier approval, or booking control that they do not have.
The advisor owns the conversation that turns interest into a decision: clarify dates, travelers, accessibility needs, budget boundaries, priorities, and acceptable trade-offs. The advisor compares available options and explains the terms attached to each one. A subagent, where the current account arrangement permits it, can carry out specific search, quote, or booking tasks within an agreed scope. The client should know who is advising them, who will make the booking, and which business will handle follow-up.
Verify RateHawk access before building a network around it
RateHawk’s current public overview presents a B2B booking service for travel professionals, including accommodation and other travel services, and describes tools such as Selection, Pay by Link, Net and Gross work models, and payment by invoice, card, or credit limit. Actual availability and conditions depend on the account, booking, and applicable terms; the live account and confirmed booking record should guide the agency’s workflow. (RateHawk travel-professional overview)
RateHawk also published a subagent operating model on August 20, 2021. That article described a master account able to add subagents, view their bookings, set individual credit limits or access to the master’s credit limit, set individual commission, and edit vouchers and invoices. It directed interested partners to contact their account manager. This is a dated feature description, not proof that every current account, territory, or legal entity can use the same model today. Before recruiting around it, ask the account manager for current written instructions, eligibility, available roles, account responsibility, and payment terms. (subagent operating model)
Do not solve uncertainty by sharing a master login. If individual access is available, create a named user for each person and grant only the permissions required for the assigned work. If the arrangement cannot provide appropriate individual access, pause the booking work until the account manager confirms a compliant process. Record who can see client details, create or change bookings, issue documents, and contact supplier support.
Put responsibility and commission in writing
A workable agreement answers operational questions before the first booking. Identify the business that contracts with the traveler, who collects the traveler’s authorization, who enters the booking, who verifies the selected room and rate conditions, who sends the confirmation, and who handles changes or complaints. Define the point at which work is reviewed and what happens when a person leaves the network. Personal data and booking records should be shared only to the extent needed for the service and under the rules that apply to the agency and its customers.
Then document the money flow: the commission basis, the party that calculates it, the records used for reconciliation, when a commission becomes payable, how cancellations or amendments are treated, who bears any credit exposure, and how disputed amounts are resolved. Do not invent a standard percentage or assume that a dashboard, account role, or verbal promise replaces the actual agreement.
RateHawk’s July 2024 commission-repayment update describes a process limited to partners using the ETI and SMETA legal entities. It discusses Master and Finance roles and withdrawal options, but its stated scope is specific. It should not be generalized to every RateHawk partner or treated as the subagent commission contract. Confirm the applicable process for the particular account and legal entity, and keep the agency’s own subagent agreement consistent with those terms. (Commission-repayment update)
Keep the traveler’s booking distinct from agency extras
The traveler-facing quote should show the supplier service, the terms that matter to the choice, the agency’s work, and any separately priced extra. A custom itinerary, a local guiding session, or an attraction plan is the agency’s service only when the agency is actually providing it. If a comparable item is available in the traveler’s RateHawk account and is booked through the supplier, follow the RateHawk item’s displayed price, payment, cancellation, and servicing rules. Do not represent an independent service as supplier inventory or charge twice for the same work.
For an independent add-on, write down its deliverable, fee, schedule, revision limits, cancellation terms, and responsible provider. If the work and agency qualify under Ruul’s current terms, its invoice and ledger entry belong to that service. They do not change a RateHawk booking’s payment or commission schedule. If an extra is charged as part of a RateHawk booking, follow that item’s RateHawk workflow and terms. (Ruul Get Paid) Ruul’s standard payment requests accept only digital services, as. Keep in-person guiding, accommodation, and transport payments on their appropriate supplier or payment route.
Follow one inquiry across the handoffs
Consider a hypothetical traveler who finds an advisor through a creator’s neighborhood guide and asks for a long weekend near the coast. The creator sends the inquiry with the traveler’s permission; the creator does not choose a rate or imply that a room is reserved. The advisor confirms dates, guest needs, budget, and non-negotiables, then explains the trade-offs among the live options. If the account’s approved subagent model allows another agent to search or prepare the booking, that agent records the source and terms of the option and returns it for the agreed review. The advisor obtains the traveler’s approval before the authorized booker places the reservation and sends the booking reference and conditions.
Suppose the traveler also asks for a digitally delivered walking-route plan. The agency defines that work as a separate deliverable, names who will provide it, and states its own fee and timing. If the service is not a bookable RateHawk item, the agency does not include it in the supplier reservation. If the service is eligible for Ruul, the agency may invoice that independent work on Ruul’s terms; the payment record remains separate from the hotel booking. This example is a workflow illustration, not a promise that every account supports the same roles or that every route, room, or add-on is available.
Make quality visible in the handoff
A network needs a small shared record, not a complicated bureaucracy. For every inquiry, capture the client’s requirements and what remains uncertain. For every recommendation, retain the options reviewed and the reason the selected terms fit. Before booking, obtain written client approval for the specific itinerary and price. After booking, record the reference, the supplier conditions, who sent the confirmation, and the person responsible for follow-up. When plans change, update the client and the relevant booking record through the approved route.
Use a recurring review to compare the booking record with the client’s instructions, identify avoidable errors, resolve commission differences, check that access still matches each person’s role, and learn from complaints or amendments. The purpose is to improve the handoff and protect client trust, not to claim that one network model guarantees better rates, fewer cancellations, or higher revenue.
Before adding a creator or subagent
- Is this person creating content, referring an inquiry, advising a traveler, or operating a booking? Name each role separately.
- Has RateHawk confirmed that the account can currently use its subagent model, and supplied the applicable instructions and terms?
- Does each person have an approved identity and only the access needed for their task?
- Is the client told which business is advising, contracting, booking, collecting payment, and providing support?
- Are commission basis, payment timing, cancellation adjustments, credit exposure, reconciliation, and offboarding written down?
- Are independent itinerary, guide, or planning services separately scoped and invoiced from supplier bookings?
- Can the agency trace client approval, booking terms, changes, and final follow-up?
| Role | May own when agreed | Does not automatically receive |
|---|---|---|
| Creator | Destination content and a permission-based inquiry handoff | Booking authority, supplier access, or a commission |
| Advisor | Client brief, recommendation, quote explanation, and follow-up | Power to change supplier terms or guarantee availability |
| Master user | Approved account administration and network oversight | Universal permission to set terms outside the supplier agreement |
| Subagent | Defined search, quote, or booking tasks under current access | Authority beyond the account role or a guaranteed payout |
Treat this as a conversation aid, not a substitute for the current RateHawk agreement or a legal contract. Adjust the role map to the actual account, jurisdiction, service, and written agreement.
A creator network can widen the path by which travelers discover an advisor. A subagent arrangement can distribute defined operational work. Neither should blur who owes the traveler a clear recommendation, who controls a booking, or how each party is paid. Start with the current supplier terms, agree the boundaries in writing, and expand only when the agency can preserve the same standard of communication and recordkeeping.
