Choose a link from a specific data flow: what information needs to be sent from where to where, and who will use it afterwards?
Show the retyping on screen
Ask your team where data is transferred from one system to another. Think of entries, payments or information for the accounts.
For each action, note down why it is necessary. Sometimes an interface between systems is relevant; sometimes a clearer working arrangement is already a good first step.
Describe what you’d like to swap
“The systems need to work together” is a start. Make the request more specific before discussing the possibilities.
- unknown nodeunknown nodeunknown nodeunknown node
Walk through one recognisable example
Take, for example, a booking that is made online and is subsequently amended. Discuss which systems and colleagues need to be notified of that change.
Also go through the exceptions. What do you expect in the event of a cancellation or a refund? This will help you clarify which information is important for your working methods.
Give an example. A brief description of your current process is more helpful in a conversation than just a list of system names. Use sample data.
Discuss the connection to Tilia
On the integration page, you’ll find Tilia’s integration links for payments, accounting and parking systems. There’s also information about the API and webhooks for setting up your own connections.
The right setup depends on the tools and data your business uses. You should therefore compare the desired data exchange with your day-to-day work before making any decisions.