Skip to main content

📞 Vlge Phone Support Agent (AI)

All the information about the Vlge Phone Agent and what they know

⚡️ NOTE: Vlge Pro Required + Add-on for AI Phone Support

HOA Support Line (Alex) - What the assistant can see and where it comes from

This guide is for HOA board members, committee volunteers, and community administrators who use Vlge. It explains what Alex can answer on the phone, what Alex cannot access, and where in Vlge the information comes from so you know what to keep up to date.


What Alex is

Alex is Village's phone support assistant on the HOA Support Line. Alex does not search the internet or use a separate document library. Answers come from your community's live Vlge data - the same records residents see in the portal, plus governing documents that Village has indexed for community search (the same document search used by your built-in AI in the app).


Verification - required before answering questions

Alex must verify the caller before answering any community-specific question. That includes rules and CC&R questions, not just billing or account details.

Caller ID alone is not enough.

Alex confirms identity using:

  • The phone number on the resident's Vlge profile (matched to the number they are calling from)

  • The community name

  • A 4-digit Phone verification PIN the resident sets in their Vlge profile

👉 Residents set the PIN here: Resident portal - Profile - Phone verification PIN

Until verification succeeds, Alex will not look up governing documents or share account information.

If the resident has no PIN yet: Alex will ask them to sign in to Village, set a PIN in Profile, and call back.

If verification fails (wrong PIN, no matching account, or too many wrong attempts): Alex will not continue with document or account lookups. After too many wrong PINs, verification locks temporarily for security. Alex can offer to submit a support ticket for staff or board follow-up instead.


Is phone support turned on for our community?

Phone support must be enabled for your community in Village before Alex can verify residents and help with community questions.

Your Village administrator or Vlge support team can confirm this is active. If it is not enabled, Alex will direct callers to the resident portal or your usual management contact - not document or account help on the phone.

Support ticket submission from the phone also requires Ticket Support to be turned on for your community under your ticket settings.


What Alex can answer - and where that information lives in Village

Governing documents, CC&Rs, bylaws, and rules

Verification: Required

What residents might ask: "What do our CC&Rs say about pets?" "What are the parking rules?" "Where is the fence height limit?"

Where you maintain this in Village:

Content

Where admins manage it

CC&Rs, bylaws, rules (PDFs and structured text)

Admin - Key Documents

CC&R sections

CC&R content in Village

HOA bylaws (when your community uses them)

Bylaws

Resident-visible community documents

Community Documents folders set to All members

How Alex uses it: Village searches indexed text from those sources and gives Alex short passages, not full PDFs to read word-for-word. Alex will summarize and reference section titles or numbers when helpful.

What is not included:

  • Board-only or staff-only document folders

  • Documents that were uploaded but never indexed for search (they may appear in a list but won't answer questions until indexed)

  • Internal board packets or meeting materials unless they are published to an all-members folder and indexed

Resident portal mirror: Community Home, CC&Rs, Bylaws, and published community documents.


ACC guidance - architectural rules (not a specific application)

Verification: Required

  • What residents might ask: "Do I need ACC approval for a patio?" "What's allowed for paint colors?"

  • Where you maintain this: Admin - ACC Guidance Items (published items only - not drafts or archived items)

  • Alex can also pull related language from CC&Rs, bylaws, and rules in the document search above.

  • Important distinction: This is policy and guidance. It is not the status of someone's fence application or remodel request.


Architectural reviews - A resident's ACC applications

Verification: Required

  • What residents might ask: "What's the status of my fence request?" "Was my application submitted?"

  • Where you maintain this: Admin - ACC (submissions queue). Residents see their own items under My ACC Requests in the portal.

  • What Alex sees (recent activity, roughly the last 90 days):

    • Submitted applications - status, request number (for example ACC-…), whether review is pending or complete

    • Drafts - saved in the portal but not submitted. Alex should not describe drafts as pending with the committee.

  • What Alex cannot do: File a new ACC application, upload plans, or change ACC status on the call.


Violations and notices

Verification: Required

What residents might ask: "Do I have an open notice?" "Was I fined?"

Where you maintain this: Violations and notices workflow in Village (staff and board tools). Notice types and labels come from your Notice Action Types configuration.

What Alex sees (recent activity on the caller's own unit or units, roughly the last 90 days, limited number of records):

  • Notice or violation type

  • Whether it is a courtesy notice, warning, fine, or legal action (using your configured labels)

  • Short description

  • Open or resolved status

What Alex does not see or do:

  • Photos or full violation history beyond recent limits

  • Board-only internal notes

  • Other owners' violations

  • Waiving, resolving, or editing notices

Alex is instructed to use the word notice when appropriate and not call a courtesy notice a fine.


Billing, balances, late fees, and payments

Verification: Required

What residents might ask: "What's my balance?" "Why was I charged a late fee?" "Did my payment go through?" "Is auto-pay on?"

Where the data lives in Village:

Information

Where it comes from in Village

Current balance and overdue amount

Unit account for the resident's property

Which property the resident is tied to

Unit ownership and occupancy records

Recent charges (dues, assessments, late fees, interest, and similar)

Posted unit charges

Recent payments

Payment history

Pending or failed payment attempts

Payment processing records

Refunds

Refund records

Saved payment methods

Resident wallet (Alex may only refer to last four digits)

Auto-pay enrollment

Resident auto-pay settings

Late fees - important for admins and residents:

  • Alex can see late fees that have already been posted as charge line items on the account.

  • Alex does not have a built-in readout of your billing policy settings (grace period, percentage, schedule). Those are configured under Admin - Financials - Dues Billing and related billing settings.

  • If late-fee rules are written in your CC&Rs or rules and those documents are indexed, Alex may summarize that written policy after verification. Otherwise Alex should explain what has already been charged or suggest follow-up through a support ticket or your management contact.

What Alex cannot do on billing:

  • Take a one-time payment over the phone

  • Turn off auto-pay (Alex can help turn auto-pay on with explicit confirmation where a payment method has already been entered - but Alex cannot take a new payment method.)

  • Change due dates, waive fees, or post adjustments

  • Read full card or bank account numbers


Support tickets

Verification: Required

What residents might ask: "Can someone from the board call me back?" "I need help with something you couldn't fix on the call."

Where tickets go: Admin - Tickets, same queue as portal tickets.

  • Alex creates tickets with the contact reason Phone Call Follow-up. You can configure routing email for that reason under Admin - Tickets - Settings - Contact Reasons.

  • Alex can also see the caller's own recent tickets (roughly the last 90 days, limited number) when answering account questions.

  • Alex cannot freely browse or edit all tickets in the system - only what applies to that verified resident.


Call summary email

After a verified call, Village may email the resident a short summary of the conversation to the email on their profile. This is not a full transcript of everything Alex looked up.


What Alex cannot access - summary

  • Other residents' accounts or units

  • Board-only documents and internal materials

  • Full PDF documents verbatim (only searchable passages)

  • Billing policy configuration as a settings screen (only posted charges plus document text)

  • Meetings, elections, reservations, or amenity booking on this phone line

  • Creating or editing ACC submissions, violations, charges, or payments (except helping enable auto-pay with confirmation)

  • Legal advice (Alex can explain what documents say, not tell someone what they should do legally)

  • The resident's PIN or full payment account details


Limits that affect answers

Limit

What it means

Recent history window

Violations, ACC applications, and support tickets are mostly drawn from roughly the last 90 days

Number of items

Alex may only see a limited number of recent violations, ACC items, tickets, payments, and charges per call

Multiple units

Balances may be combined; Alex may emphasize the primary unit

Same phone, multiple communities

Resident must confirm community name and PIN

Missing or unindexed documents

If Village cannot find a passage, Alex should say so - not guess


Admin checklist - keep Alex accurate

  1. Confirm Voice Support (Alex) is enabled for your community.

  2. Upload and index Key Documents under Admin - Key Documents.

  3. Keep resident-facing Community Documents in all-members folders and indexed.

  4. Publish ACC Guidance items (not left as drafts) for architectural policy questions.

  5. Configure Notice Action Types so courtesy notices and fines are labeled correctly.

  6. Turn on Ticket Support if you want phone escalations; set up Phone Call Follow-up routing email.

  7. Ask residents to add a phone number and 4-digit PIN in Profile before they call - required even for rules questions.

  8. For late-fee questions: either post charges correctly so they appear on the account, or document the rules in indexed governing documents.


Quick reference - resident question to Village location

Resident question

Verification needed?

Where admins maintain the answer

"What do CC&Rs say about pets?"

Yes

Key Documents, CC&Rs

"What's the fence rule?"

Yes

ACC Guidance, Key Documents

"What's my balance?"

Yes

Financials, unit charges

"Why was I charged a late fee?"

Yes

Posted charges; billing settings; governing docs if written there

"Do I have an open notice?"

Yes

Violations and notices

"Status of my fence ACC request?"

Yes

ACC submissions queue

"Please have the board follow up"

Yes

Tickets settings

"Turn on auto-pay"

Yes

Resident wallet and auto-pay settings

🛟 Need more help? Just ask!

Did this answer your question?