Axela

Create a support ticket linked to a unit or HOA the current user has access to. Use this when the user explicitly asks to open a ticket, submit a request, or report an issue to the Axela team; always confirm the ticket content with the user before calling this tool. Optionally pass a requestTypeId from ListClientTicketRequestTypes; when omitted or invalid, the ticket falls back to the 'Other' category. The response includes the stable ticketId; keep it and use it with ReplyClientTicket for follow-ups instead of listing tickets again.

create_client_ticket

Fetch client invoice data: the list of invoices with their status, plus totals grouped by status (sent, paid, canceled, returned, rejected). Use this tool whenever the user asks about invoices billed to their community or a specific unit. Clients are automatically scoped to their communities; filtering by HOA or unit is optional for them. Filters: HOA code or ID, unit code or ID, and invoice status. Date range: - Prefer using lastNDays (e.g., 90) for relative time windows like 'last 3 months'. The server computes fromDate/toDate using current system time. - Use fromDate/toDate only when the user provides explicit dates. - If no range is given, the search covers the last 7 years.

find_client_invoices_data

Fetch disbursement data (checks sent to the association): amount totals by status (cashed, pending, processing, returned) and the list of disbursement checks. Use this tool whenever the user asks about disbursements, checks, payouts, or money sent to their community. Clients are automatically scoped to their communities; filtering by HOA code or HOA ID is optional for them. Date range: - Prefer using lastNDays (e.g., 90) for relative time windows like 'last 3 months'. The server computes fromDate/toDate using current system time. - Use fromDate/toDate only when the user provides explicit dates. - If no range is given, the search covers the last 7 years. The detailed check list is only included when the range is 45 days or less, or when filtering by a specific HOA; otherwise only totals are returned.

find_disbursements_data

Fetch info for a single homeowners association (HOA/community). Data may include balances, units in collection, units in dispute or payment plans, etc. Also returns the client approvals pending on the HOA (escalation / legal action, bankruptcy proof of claim, lien, sale authorization) with the escalation and bankruptcy units broken down in unitsInfo. Prefer a valid HOA ID (GUID) when known; otherwise use the HOA code, the external ID, or a search term. Use when user asks for HOA using search term like code, name, a unit code (e.g., ABCD-1234 → HOA ABCD), or a ticket code (e.g., ABCD-1234-5678 → HOA ABCD). When the user identifies the HOA by its id in their own management software, in any wording (source id, sourceId, external id, external source id, integration id, association id, CINC id, Vantaca id) or a plain number/code that is not an HOA code or GUID, pass that value as externalId, NOT as hoaId, hoaCode or searchTerm. If query is general (e.g., "list all my HOAs"), call listHoaNames first.

find_hoa_data

Fetch legal invoices for enforcement action, mortgage foreclosure, bankruptcy, or probate for one unit or HOA. Use this tool when the user asks about legal invoices, attorney fees, litigation fees, or legal costs. Filter with at least one UnitCode, UnitId, HoaCode, or HoaId. If only a name or address is known, use FindUnitsData or FindHoaData first. Client access is automatically restricted to the user's HOAs, and Pending or Canceled invoices are excluded for clients.

find_legal_invoices_data

Fetch the outreach history of a unit or HOA the user has access to: calls, emails, SMS and notes, a conversation summary, and the owner sentiment analysis with the Willingness to Pay Score. The analysis and the score are produced by the Axela platform from the unit's account and outreach records and are the same ones the user sees in their Axela portal; the tool only reads them. Use it when the user asks about a unit's outreach or communication history, sentiment or tone, payment intent, or willingness/likelihood to pay. Date range: - Prefer using lastNDays (e.g., 30) for relative time windows like 'last 30 days'. The server will compute fromDate/toDate using current system time. - Use fromDate/toDate only when the user provides explicit dates. - When no range is given and the search targets a specific unit or HOA, the full outreach history is returned. Filters: HOA code (optional), Unit code (preferred). Important: - If the user targets a specific unit via name/address/email/phone (no unit code), call FindUnitsData first to resolve the unit code, then call this tool. - If no unit is specified, ask for a unit identifier (name/address/email/phone), use FindUnitsData to get the unit code, then call this tool.

find_outreach_data

Fetch a property unit of an association the user has access to, with its related data: address, owner and contact details, amount owed, collection status, disputes, payment plans, liens and foreclosure data, estimated home equity, pending client approvals (escalation / bankruptcy proof of claim), outreach sentiment with the Willingness to Pay Score, and open Support / Legal Action tickets with their thread (ticketHistory). This is the same account data the user sees for the unit in their Axela portal; the tool only reads it. When the result resolves to a single unit, it includes its open tickets: use it to get a ticket's context (e.g. what a ticket like ABCD-1234-5678 is about) when ListClientFollowedTickets does not return it. A unit can be searched by (in this priority order): valid unit ID (GUID), unit code, external ID (the unit's account/id in the client's own system), address, name, owner/person name, email, or phone. Always use the unit ID when it is known; otherwise use the unit code, external ID, or search term. A ticket code embeds the unit code: ABCD-1234-5678 → unitCode ABCD-1234. If the user requests details for multiple known units, invoke this tool once per unit using each unit's search term.

find_units_data

Aggregate the unit book across every HOA the user can access, a named subset, or the HOAs a management company oversees: units and balances by collection status, stage and tag, plus one row per HOA. Use it for portfolio-wide questions such as 'how many units do I have in Collection Notice', 'which of my HOAs has the most units above the threshold', 'total balance in collection across my associations' or 'units in collection under Associa'. Optional filters narrow the units (collection states, stages, tags, lien filed, pending approval, balance range, collection start and close periods; any-of within a list, all combined); quote the figures from summary and byHoa, never count rows yourself. For 'the highest unit balance' or 'my top N units' ask for topUnits: two rankings kept apart, units in collection by Axela's ledger and units not yet in collection by the client's system, each with HOA, owner, stage and status; never probe minBalance for a maximum. For one HOA's detail use find_hoa_data. Administrators must scope the call: hoaCodes, or a management company (managementCompany / managementCompanyId); the whole platform is never aggregated.

get_portfolio_metrics

Securely Retrieve comprehensive financial information for a property unit, including payment history, late fees, current balance breakdown, and payment plan status. Use this tool if the user asks for financial information about a unit that is already identified by unitId or unitCode.

get_unit_accounting_data

List up to 10 open Support and Legal Action tickets created by or followed by the current user, prioritizing tickets they created and then most recent activity. Use this when the user asks about their tickets, requests, or pending support conversations, or to resolve a ticket ID before replying with ReplyClientTicket. A ticketCode embeds its unit and HOA codes ({UnitCode}-{suffix}, e.g. ABCD-1234-5678 → unit ABCD-1234, HOA ABCD); to look the unit up, prefer linkId as unitId.

list_client_followed_tickets