Sign in to Fortress OSIntegration Partner · Collections
Hunter Warfield + Fortress OS
Hand off delinquent accounts to Hunter Warfield on rules you set, at every property, on the same terms.
Updated · 3 min read
What is the Hunter Warfield + Fortress OS integration?
Hunter Warfield is a collections agency. Fortress OS hands off delinquent former-resident accounts on rules you set: how long an account stays in house, the smallest balance worth pursuing, and the type of collection. The handoff runs on those rules, so it never waits on somebody's calendar reminder.
Key takeaways
You set how many days an account stays in house before handoff.
You set a minimum balance, so small debts stay out of the handoff.
Turning automated collections on or off asks you to confirm first.
How does Hunter Warfield work with Fortress OS?
You configure automated collections per property in Integrations Setup. You choose the collections agency, the number of days an account stays in house before handoff, the minimum account balance that qualifies, and the collections type. From then on the handoff runs on those rules.
What data flows between the two?
Fortress checks delinquent accounts against the thresholds you set. An account that passes both the days-in-house rule and the minimum balance goes to the agency. Because you set the rules per property, the answer to why an account went out is a setting your team can point at.
Who handles the setup?
Our integrations team handles documentation exchange, API keys, and end-to-end testing. Most Hunter Warfield connections go live in a few weeks. You can request a setup any time.
Why should you connect Hunter Warfield to Fortress OS?
A collections policy written in a document gets applied when someone has time that week, which means it gets applied differently at every property. Writing the policy into Fortress makes it run the same way at the sites your regional visits every month and the sites they do not.
What changes once you connect Hunter Warfield?
Same collections tool. Different day-to-day for your team.
| Daily task | Without the integration | With Fortress OS + Hunter Warfield |
|---|---|---|
| Deciding what goes to collections | A policy in a document, applied when someone gets to it. | Days in house and minimum balance, enforced per property. |
| Sending accounts to the agency | Someone builds the file by hand and emails it. | Accounts hand off when they cross your thresholds. |
| Small balances | Sent anyway, or missed. | Your minimum balance keeps them out of the handoff. |
| Turning it off | You tell everyone and hope the message lands. | You switch it off on the property, with a confirmation step. |
Tags
- Hunter Warfield
- Hunter Warfield integration
- Collections
- Fortress OS
- integration
- property management software
- affordable housing
Frequently asked questions
Quick answers about how Hunter Warfield and Fortress OS work together. Don't see your question? Ask us →
What can we control about the handoff?
The collections agency, how many days an account stays in house first, the minimum account balance that qualifies, and the collections type. You set all four per property.
Can we stop small debts from being sent?
Yes. The minimum account balance setting keeps accounts under your threshold out of the automated handoff.
Can automated collections be turned off?
Yes, per property. Turning it on and turning it off both ask you to confirm, because it changes what happens to real resident accounts.
Do we contract with Hunter Warfield directly?
Yes. The agency relationship is yours. Fortress handles the handoff so the policy you agreed on runs the way you wrote it.