Agency trips are private working records. Build them carefully, review them internally, and only then create client-safe proposals.
Start a trip
Depending on enabled pilot features, an agency trip can start from a blank trip, an approved template, an approved Trip Brief, a text-based PDF import, or an AI-assisted draft. Use Advisor-reviewed Trip Briefs when client intake needs review before becoming planning instruction.
Choose how AI uses the brief
When strategy controls are enabled, choose the planning approach before drafting:
- Use as inspiration lets Platix design the route and discover places that fit the brief.
- Preserve must-dos keeps the exact places you approve and fills sensible gaps around them.
- Follow places exactly limits ordinary activity discovery to the Google-verified places you approve.
The last two options pause for a place review. Check the verified names and addresses, remove anything that should not be authoritative, and clarify any unresolved venue before creating the draft. The resulting trip stays private and continues through the same review lifecycle as other agency trips.
Keep the trip assigned to the advisor or team member responsible for the client work.
Review before delivery
Check dates, overnight bases, stop order, transportation, supplier details, practical notes, and client-specific requirements.
Use manager review when the agency requires approval before proposals or final delivery. Review comments belong in the agency workspace and should not be copied to clients unless intentionally rewritten for client-facing use.
Keep internal work private
Internal notes, net costs, supplier references, private booking records, and unfinished ideas should remain inside the agency trip.
A proposal is the selected client-safe snapshot. Do not send the raw agency workspace as the client review surface.
Update the trip after feedback
When a client asks for changes, update the trip first. Then create or publish a revised proposal version if the client needs to review the changed itinerary.