ASTA VTA common mistakes
ASTA VTA · Understand the traps and how to avoid them.
Treating supplier commission or incentive payments as the advisor's own money and quoting a client a price that omits the agency's service fee, then discovering the fee cannot be added later.
New advisors often come from a retail mindset where the displayed price is the whole transaction, and they have not yet internalized that the advisor's compensation is usually a supplier-paid commission separate from any client-facing fee.
What to do instead
Before quoting, write out the full price stack: supplier net, taxes and fees, agency service fee, and any optional insurance or transfer costs. Disclose the service fee in writing at the point of engagement and confirm the client accepts it before any booking is made.
Accepting a client's verbal instruction to change or cancel a booking and acting on it without written confirmation, then being unable to show who authorized the change when a penalty is disputed.
Advisors want to be responsive and fast, and phone or text feels friendlier than email; the gap is that verbal instructions leave no defensible record of scope, timing, or consent.
What to do instead
Adopt a rule that no change or cancellation is executed without a written instruction from the client or a written record of the call sent back for confirmation. Log the date, time, channel, and the client's exact instruction in the booking file.
Recommending a destination or itinerary based on personal travel experience alone, without checking current entry requirements, seasonality, or supplier operating status.
Personal enthusiasm is persuasive and easy to reach for, but conditions change constantly and a single past trip is a snapshot, not current intelligence.
What to do instead
Build a pre-proposal checklist: verify visa and passport validity rules, health entry requirements, seasonal weather and closures, and supplier confirmation status for the specific dates. Cite the source and date checked in the client file.
Selling a destination as interchangeable with a similar one (for example, treating two island nations or two European capitals as equivalent) and mis-setting client expectations about cost, language, or infrastructure.
Surface similarities in climate or marketing imagery lead advisors to reuse a proposal template without validating the differences that matter to the specific client.
What to do instead
For each proposal, list three concrete differentiators relevant to the client's stated priorities, such as transfer times, accessibility, cuisine, or peak-season pricing, and confirm them against current supplier information before sending.
Presenting a single option in the first proposal instead of a structured choice, which stalls the decision and pushes the client to shop the itinerary elsewhere.
Advisors fear overwhelming the client and default to one 'best' recommendation, but a single option gives the client nothing to react to and no sense of value range.
What to do instead
Present two or three clearly differentiated options with a short line on who each suits and the trade-offs between them. Ask a closing question that requires a choice rather than an open 'what do you think'.
Not qualifying budget, decision-makers, and travel dates before investing hours in a detailed itinerary.
Enthusiasm to demonstrate expertise leads advisors to build first and ask later, and clients are often vague when asked open-ended questions about money.
What to do instead
Use a fixed intake script covering budget range per person, who else must approve, hard date constraints, and must-have versus nice-to-have items. Record answers in the CRM before any itinerary work begins.
Failing to document the booking file with client communications, supplier confirmations, and waiver acceptances, leaving the agency exposed when a dispute arises months later.
Documentation feels like overhead during a busy selling period, and advisors assume email history is sufficient when it is scattered across inboxes and phones.
What to do instead
Set a standard file structure and a rule that every booking contains the signed terms, the client's written acceptance of cancellation terms, supplier confirmations, and a dated contact log. Audit a sample of files monthly.
Mishandling client funds by depositing them into a general operating account rather than a segregated trust or client account where local rules require it.
Small agencies often start with one bank account for simplicity and do not realize that client money may carry separate legal handling obligations until a supplier fails or an audit occurs.
What to do instead
Confirm with a qualified local advisor or regulator what client-money rules apply, then open and use a dedicated account with reconciled records if required. Document the reconciliation process and review it quarterly.
Assuming that because the advisor is home-based or works under a host agency, the host's registration, bonding, or seller-of-travel credentials automatically cover the advisor's own activities.
Host agency marketing emphasizes that affiliates can 'start fast', so advisors skip verifying which obligations sit with the host and which remain with the individual or the advisor's own entity.
What to do instead
Obtain the host agreement and read the sections on registration, bonding, errors and omissions coverage, and who is responsible for compliance. Confirm in writing which credentials apply to the advisor and keep that record on file.
Advising on passport validity, visas, or health requirements from memory instead of directing the client to the official issuing authority and documenting that referral.
Advisors want to be helpful and confident, but entry rules change frequently and giving an incorrect answer can create liability that a documented referral would have avoided.
What to do instead
State the general principle (many destinations require validity beyond the return date) while directing the client to the relevant embassy, consulate, or official government site for their nationality. Record in the file that the client was referred and is responsible for verifying requirements.