Contact data drives the following Aiwyn behavior.
| Behavior | Who it affects | Detail |
|---|---|---|
| Receives invoice emails | Firms that do not use a mail rule to route Aiwyn invoice emails | The contact-level flag decides whether Aiwyn emails this person an invoice. Firms that do use a mail rule - most firms - have Aiwyn respect whichever recipients they addressed the invoice email to. |
| Receives statement emails | All firms | Aiwyn looks up every contact on a client whose AR has aged past the firm's collection triggers and emails the ones flagged to receive statements. |
| Receives payment notification | All firms | Contacts set to receive payment notification emails (receipts). Typically, contacts set to receive invoices are usually set to receive payment notifications. |
| Client portal account linkage | All firms | Where the same contact email address appears on more than one client in the Practice Management System, the portal user's client accounts will be linked to their user automatically. |
| Engagement letter primary contact | Firms using Engagements | The default primary contact of an Engagement Letter. A contact is still designated as primary if firm does not use Aiwyn Engagements however it has no further impact or function. |
| Engagement letter billing contact | Firms using Engagements | The default billing contact of an Engagement Letter. A contact is still designated as the primary if the firm does not use Aiwyn Engagements however it has no further impact or function. |
| Contact removed from a client | All firms | Aiwyn inactivates the contact-to-client link, so the contact stops receiving that client's invoices and statements. It does not remove the client entity from an existing client portal user. |
Related
- How Aiwyn creates client contacts from your system
- Client contact fields and where Aiwyn uses them
- What happens when you remove a contact from a client