Integrations Insightly
InsightlyPlanned

Insightly relationships, connected to support.

Plan an Insightly connector that helps agents understand a customer’s organization and ownership without copying the whole CRM.

Planned connector. Native setup is not available yet. The workflows below describe the intended scope; release depends on provider access and testing.

CRM

What we’re planning to connect.

  1. 01Insightly
  2. 02Planned connection
  3. 03Message support
01

Map the organization

Associate the support customer with the intended organization and relationship record.

02

Route a handoff

A proposed owner field would help the agent direct a customer request to the right account contact.

03

Keep project context minimal

If project context is selected, show a useful reference or status instead of unrestricted project notes.

The right context

Be precise about what connects.

Define the data, permissions and destination before putting the workflow in front of customers.

Contact and organization

Relationship owner

Selected project reference

Message Inbox keeps the customer conversation together. Shown: Message’s current workspace, not a preview of the planned connector.
Prepare for the connection

Define your first workflow.

  1. 01

    Choose the first workflow

    Agree on the contact-to-organization mapping and which project references are useful for support.

  2. 02

    Agree on data and permissions

    Decide which fields may be read, which people may use them and whether any separate write action is needed. Native setup is not available yet.

  3. 03

    Define the acceptance test

    Test a person related to multiple organizations so the correct business context remains explicit.

Before you connect

Insightly integration questions

Can I connect Insightly to Message today?

The native connector is planned. The workflows on this page describe the proposed design; there is no native installation to activate yet.

What should we test before using it with customers?

Test a person related to multiple organizations so the correct business context remains explicit.