Kilango shows what your customers keep asking about, pulled from the systems you already work in. You set the portal up in the studio and publish it on your own domain, without building anything.
Kilango is closed right now. Access is by invitation, and a human sends it.
The same product, three brands. A brand picks a logo, one primary colour, the colour of the navigation and a font. Everything else is fixed, so status reads the same in every portal.
There are three things to understand, and they are the same whether your customer is a client, a contractor or a supplier.
An app in Kilango is Productive, Pipedrive, Dalux or Fynk, not a feature we invented. You connect the app once and turn it on for the portals it belongs to.
You give a person access to one portal, as part of an organisation. The organisation is linked to a record in the source system, and that link decides which data comes through.
When a customer asks why they cannot see their report, you open the portal exactly as they see it. The session is read only, lasts 15 minutes and shows up in the activity log afterwards.
Once the invitation is there, it is three steps, and you do them yourself in the studio.
A name, an address and one primary colour. The palette is derived, so the portal looks finished from the first screen.
Pick the app for the system your customer asks about, and paste the key. Kilango finds the records that can be linked.
Invite the person, link the organisation, and publish the portal. The checklist in the studio says what is still missing along the way.
Kilango is closed, and access is by invitation. There is no self serve and no waiting list: we read the request and invite you when there is room.
Already invited? The way in is in your inbox. Log in to the studio.