Intelliflo Office
The Intelliflo Office app connects Templi to your Intelliflo Office (IO) tenant. Once connected, you can import your advisers and clients, have Templi fill the Intelliflo fact find from meetings and files, export the completed fact find back onto the IO client record, and ask Templi questions that it answers from live IO data.
What it does
Imports your book. Every adviser and client in IO can be brought into Templi in one pass, with family groups and relationships recreated. See Import your clients.
Fills the fact find. Connecting creates an Intelliflo Fact Find template and makes it your firm's default. Templi completes it from the IO record, your meeting transcript and attached files.
Writes back. Exporting a completed fact find updates the IO client record. Templi creates the client in IO first if they are not already there.
Keeps plans in step. Plans import with their fund holdings, valuations and contributions, and a plan you have corrected in Templi can be sent back to IO. See Send a plan to your CRM.
Answers from IO. Ask Templi about a client and it reads their IO plans, fees and expenditure directly, so the answer cites the record rather than a copy.
Uses IO documents. Files held against the client in IO can be attached as sources when Templi drafts a report.
Before you connect
Templi is bought through the Intelliflo App Store and billed by Intelliflo at £15 per user per month. Purchase it there first.
You need administrative access in IO to authorise the connection, and an administrator login in Templi.
The connection is shared by your whole firm. It is made once.
Connect
In Templi, click Integrations, open Intelliflo Office and click Connect.
Review what the app will be able to do and click Authorise and connect.
Sign in to Intelliflo in the tab that opens and approve the connection.
The general steps, and what to do if the app later asks to be reconnected, are in Connect your back-office system.
What is read and what is written back
Fact find area | Imported from IO | Exported to IO |
|---|---|---|
Personal details, contact details, addresses | Yes | Yes |
Client type (individual, trust, business, charity) | Yes | Set when Templi creates the client |
Employment and income | Yes | Yes |
Assets | Yes | Yes |
Vulnerability | Yes | Yes |
Family groups and relationships | Yes | No |
Liabilities | No, held in Templi only | No |
Dependants, goals, expenditure | Not part of the Intelliflo fact find | No |
Plans and policies | Yes, with their valuations and contributions | Yes |
Fund holdings | Yes, with ISIN, SEDOL and Citicode kept separate from the provider fund code | Yes, when the holding has units, a unit price, a valuation date and an ISIN, SEDOL or Citicode |
Documents | Read when drafting | No, Templi never uploads to IO |
Plans and fund holdings
Before IO will accept a plan it needs a plan type it recognises, a provider on your site, and a selling adviser on the IO client.
Plan type. Pension, investment, protection and mortgage each match a type on your IO site. A plan left as Other does not, so set it to one of the four before sending.
Provider. The provider name on the plan has to exist on your IO site. Correct the plan, or add the provider in IO, if the send comes back saying IO does not know it.
Selling adviser. IO takes this from the client. Give the client an adviser in IO if they have none.
On a plan IO already holds, Templi leaves IO's own plan type, workflow, selling adviser and provider alone, and keeps every owner already on the record. Valuations and contributions go across only when IO does not already hold them, so sending the same plan twice does not duplicate them.
IO matches a fund by its ISIN, SEDOL or Citicode, and needs the units, the unit price and the date they were valued. A holding missing any of those is reported back to you, and the rest of the plan still goes across.
Update a plan through chat
Ask Templi on the client's record. It changes the plan in Templi first, then asks you to approve the send.
Add a fund and send it
Add the Fidelity Index World Fund to Sarah's Aviva pension, 1,240 units at £4.83 as at 31 August, ISIN GB00BJS8SJ34, then send the plan to Intelliflo.
The fund is recorded against the plan, and IO matches it on the ISIN when the plan is sent.
Correct a plan and send it
The policy number on Sarah's Aviva pension is wrong, it should be AV-4471902. Fix it and send the plan to Intelliflo.
The approval request shows the old and the new policy number, alongside anything else that has changed since the plan last went across.
Ask what will be sent
If I send Sarah's Aviva pension to Intelliflo now, what goes across and what stays in Templi?
Templi reads the plan and answers before anything is sent.
Good to know
Advisers come across with their IO office, so one person who is registered in several IO offices has one Templi adviser record per office. That is expected, and each record is what exports bind to.
Relationship names your firm has defined in IO are mapped to Templi's standard relationships where they line up, such as spouse, parent, sibling, director, trustee or beneficiary. Anything else is kept as "other".
Client notes in IO are not read.