What counts as insurance VA AMS experience?
AMS experience is not a single credential. It includes the platform and version, the lines of business served, the role the person held, the tasks performed independently, and the controls used when something did not match. A person who updated contacts in Applied Epic may never have reconciled a carrier download in AMS360. Someone comfortable with a personal-lines queue in HawkSoft may need different training for commercial renewals or employee benefits.
Ask for concrete examples: an activity created and closed, a carrier document indexed to the right policy term, an exception sent for review, a renewal list prepared, or a client record corrected under supervision. A sanitized screen demonstration or sample work product is stronger evidence than a platform logo. Do not ask a candidate to expose a prior client's records; use your own test environment or fictional data.
The agency also has responsibilities. Its own AMS configuration may use custom activity codes, attachment labels, templates, queues, integrations, and approval rules. A provider can supply relevant insurance experience, but the agency must explain which local rules govern its book. That is why the hiring question is "Can this person run our workflow safely?" rather than merely "Have they used our AMS?"
Turn the existing process into a hiring brief
Choose one recurring task before interviewing providers. A useful first assignment might be indexing a returned policy document, preparing a certificate request for review, or recording a carrier follow-up. Write down how the work arrives, the minimum inputs, where the VA finds source records, what can be changed, who approves the output, and what closes the task.
The brief should also name the exceptions. What happens if two clients have similar names? If the downloaded document shows a different effective date? If a certificate request asks for wording that the approved policy record does not support? If a carrier response changes terms? These are the moments that reveal whether the assistant will pause and involve an agency owner.
For a larger selection process, United Alliances' guide to choosing an insurance back-office outsourcing partner covers staffing, security, reporting, and contract fit. This article narrows the decision to hands-on AMS work within an agency's existing setup.
Ask for a demonstration matched to your AMS
Give every shortlisted provider the same sanitized scenario and the same completion rule. For example, a commercial client asks about a pending endorsement. The VA must locate the correct account and policy term, find the source request, create or update the appropriate task, record the carrier contact, attach a response, and leave an unresolved coverage question with the assigned account manager. Watch the sequence and the audit trail, not only the speed of clicking.
A useful demonstration has three parts. First, let the candidate navigate a routine case and explain each record they touched. Second, introduce one missing or conflicting detail and see whether they stop rather than invent an answer. Third, ask them to show the handoff: what the reviewer sees, what remains open, and what would count as completed work. If a live sandbox is unavailable, have the candidate walk through anonymized screenshots or an agency-created sample while stating what they would verify before acting.
Score the response against your written procedure. Look for correct account and term selection, accurate source documentation, sensible escalation, and a clear next action. A fast task completed on the wrong account is a failure. A candidate who flags the mismatch and asks for review may be the safer hire, even if the simulated task remains open.
Platform names should lead to different task questions
The AMS on the agency's contract determines what to test. These examples use vendor-described features to frame interview questions; they do not establish that any particular assistant or outsourcing company has been certified by a software vendor.
| AMS named in your brief | Useful candidate demonstration | Question the agency should answer |
|---|---|---|
| Applied TAM | Locate the client and policy, record an activity, attach a document, and show the approved change-request route | Which current TAM workflow and permissions apply, and is an AMS migration planned? |
| HawkSoft | Use the agency's task and document process to show a carrier follow-up or download exception | Which Action Menu steps, labels, and reminders does this agency actually use? |
| QQCatalyst | Find the policy record, assign a task, attach evidence, and show how the next user sees it | Which task templates, alerts, and communication permissions are enabled? |
| AgencyBloc | For a health or benefits account, update the approved client or policy record and document the next enrollment or service action | Which data fields, teams, and approval rules govern this benefits workflow? |
Applied's TAM servicing curriculum includes client records, activities, attachments, policy workflows, and change requests. Applied also maintains a TAM migration resource hub. If your agency plans to move systems, specify whether the VA is being hired to support current operations, migration preparation, or both; experience in TAM should not be represented as automatic proficiency in Epic.
HawkSoft describes policy-level documents, carrier downloads, alerts, and its Action Menu. Vertafore describes QQCatalyst as an AMS with client and policy data, tasks, and workflow tools. AgencyBloc focuses on health and benefits agencies with client, policy, task, and communication records. These are reasons to ask different interview questions, not a substitute for observing the assigned person's work in your configuration.
Interview the person who will actually do the work
A sales representative can describe a company's broad software exposure, but the assigned VA's experience matters more. Ask who will work on the account, who will supervise and review their tasks, and who covers absences. If the candidate is not yet selected, make the demonstration and agency approval part of the matching process before granting live access.
Useful interview questions are specific. "Which AMS tasks have you done in the last year?" "How do you distinguish a current policy term from a prior term?" "What do you do when a download does not match the expected insured?" "Which information do you record before closing a carrier follow-up?" "When do you stop and ask a producer or account manager?" Ask for the answer in the context of your queue, not an abstract description of good service.
Separate platform knowledge from insurance authority. A VA may be able to enter a change request or prepare documents in an AMS without being authorized to recommend coverage, negotiate, or bind a policy. The NAIC explains producer licensing for selling, soliciting, and negotiating insurance. Your agency should review delegated tasks against the applicable state rules, carrier arrangements, and internal permissions.
Set up access for the assigned role, not for convenience
Start with a named account, a task-appropriate permission set, and a clear owner for provisioning and revocation. Avoid sharing an agency administrator's credentials or giving edit rights to records the VA does not need. Check both AMS permissions and any connected email, document store, carrier portal, or benefits system permissions. If the provider will use a backup person, specify how that person is approved and provisioned.
NIST's small-business cybersecurity guidance recommends multi-factor authentication where available. Agree how the agency will review access logs, handle exported files, report a suspected incident, and remove access at the end of an assignment. The provider's promise to protect data should be translated into the controls on the actual accounts used for the work.
Before the first live task, decide which changes the VA may make without review and which require a stop. Bulk data cleanup, record merges, deletion, premium changes, and client-facing coverage language deserve particularly careful approval. Test a small set of permissions with the person who will use them; an account that cannot perform the assigned task is a productivity problem, while an account that can do too much is an avoidable risk.
Onboard in the agency's workflow without redesigning it
A strong onboarding sequence begins with observing a few real but appropriately protected examples, then completing a sanitized exercise, then processing a limited live queue with agency review. Provide the VA with the agency's naming conventions, activity codes, source-of-truth rules, standard messages, and contact list for exceptions. Assign one internal reviewer who can answer questions promptly and record changes to the procedure.
During the first live cycle, compare the VA's work with the original request and the AMS record. Check whether documents landed on the correct account and term, notes identify the source and next action, open exceptions remain visible, and client or carrier communication followed approval rules. Give feedback on the exact record and step; "be more careful" is too vague to improve a workflow.
Keep the rollout bounded until ordinary and unusual cases are both handled reliably. Adding a second line of business or a higher-risk task changes the training and review requirement. If the agency is also migrating from Applied TAM to Epic, treat migration roles, data conversion, and post-migration tasks as a separate scope with the system owner and vendor; routine VA onboarding does not make someone a migration specialist.
What should you measure after the hire?
Measure whether work is accepted without rework, completed within the agreed window, documented in the correct record, and escalated on time. Include the number of eligible tasks and inspect a sample of the actual files. For AMS work, the most revealing questions are often whether the task was attached to the right account and policy term, whether an exception was hidden by closing an activity, and whether the account manager could understand the next action without retracing the entire file.
Agree when the clock begins, what pauses it, and who signs off on completion. Carrier and client waits should remain visible even if they are outside the VA's control. A weekly review can identify one instruction to clarify or one permission to adjust. The purpose is to improve the operating process, not to reward a large count of closed tasks.
How United Alliances fits an AMS-specific search
United Alliances' dedicated Insurance Virtual Assistant service describes support inside agency workflows and explicitly names Applied Epic, AMS360, HawkSoft, and EZLynx. The company's capacity article also discusses Applied TAM, QQCatalyst, and AgencyBloc as systems insurance support professionals may encounter. A published system name is a starting point for a hiring conversation; it is not proof that the assigned person has performed your task in that platform.
Bring United Alliances your actual AMS, line of business, first workflow, and review rules. Ask to meet or assess the person proposed for the work, see a task-specific demonstration, and confirm supervision, backup, access, and documentation. If your requirement is Applied TAM or AgencyBloc, request explicit confirmation of the assigned person's recent experience in that system. If it is HawkSoft, ask to see the candidate work through your particular task and document process. This lets an agency evaluate dedicated insurance VA support against evidence it can inspect.
