Settings and activity
1 result found
-
264 votes
Hi community, thanks for continuing to share how much time this workflow can take.
Right now, we're building an agent that'll sit within JAX and help you get paid without the need to manually chase your customers, which may help address some of the need for more efficient follow-up and statement management.
Initially, you won’t be able to turn this on for an entire contact group at once. You'll be able to enable it for each individual contact within a group, and JAX will do the handy work of designing a personalised plan to follow up with each one. For some this may be a consolidated statement.
We recognise this doesn't cover every part of the original idea here, including sending statements to a whole contact group in one action. We’ll keep these gaps in consideration for future improvements and will share another update once the JAX agent is…
An error occurred while saving the comment An error occurred while saving the comment 
Tim Jack
commented
Thanks for the response, Kelly. It really was tumble weed in here for a very long time. The suggestion that we can use the filters fundamentally misunderstands the gap. The existing filter on statements suggests "Contact, account no., email or postal address", whereas the functionality being requested aligns for more closely with groups (i.e. lovingly hand-crafted lists that we only wish to lovingly hand-craft, *once*) or smart-lists . Helping your customers collect payments faster is a worthy goal, but the truth is you can only move the needle so far, and the functionality being requested here has far wider use. Think hand-crafted lists. Think (for example) customers that have requested a regular statement vs those who do not. Then within that, customers who want monthly, vs quarterly. Then think customers for whom you would attach one sort of covering email (harsh but fair) vs another (harsh but fair but harsh). Those of us with some experience of development in these environments know how difficult rigging custom groups to drive statements would be so getting a timeline for delivery within the next three weeks, with delivery no later than 31-Mar-2026 would not seem unreasonable. Your immediate thoughts on those timelines would be appreciated.
An error occurred while saving the comment Tim Jack
commented
Please get this done.
Tim Jack
supported this idea
·
Hi Kelly, please listen to what the people are saying. An LLM might be the future of all workflows, but you/Xero are ignoring the very clear demand for deterministic solutions based on well-structured data that is sitting in front every user, every day but is currently useless for a basic requirement. You are trying the 3rd guess how we want to work. You have gone full clippy!. Please come back to the real world of actual requirements.