Why your callbacks belong in the calendar you already use

Salespeople do not live in one system. They live in a calendar. The site visit, the team meeting, the dentist, the child’s school function — all of it is in Google Calendar or Apple Calendar or Outlook, and that is the thing they check before they agree to anything. If twelve promised callbacks live somewhere else entirely, they are invisible at the exact moment someone says “can we speak at four?”

That is the gap this feature closes. LumaKol follow-ups can now appear as entries in whichever calendar you already use, through a private subscribe-by-link feed. There is nothing to install and no account to connect.

How the link works

You turn the feed on in the app and get a URL ending in .ics. You paste it into your calendar once, using its “subscribe to calendar” option — the same mechanism people use for a cricket fixture list or a public holidays calendar. From then on, your follow-ups appear alongside your meetings as a separate, toggleable calendar layer you can switch off when you want a clear view of your day.

The link is private and unguessable, and it is the credential: anyone holding it can read that feed, which is precisely why it should be treated like a password and not pasted into a group chat. If it ever goes somewhere it should not, rotate it in the app — the old link stops working immediately — or switch the feed off altogether.

The feed covers the fortnight behind you and the three months ahead, which is enough to see what you missed last week and to plan around commitments you have already made, while keeping the file small enough to load quickly on a phone.

What each entry actually tells you

A calendar entry that says “Follow-up” is worse than useless: you have to open another app to learn anything, which is the friction the feature was meant to remove. So each entry carries what you need to make the call without opening anything.

• The title names the person to call. If you are looking at a team feed and the lead belongs to a colleague, their name appears too, so you can tell your own work from your team’s at a glance.
• The phone number, in the location field — which on most phones means the number is tappable straight from the calendar entry.
• The lead’s current pipeline stage, so you know whether this is a first contact or a closing conversation before you dial.
• The last recorded outcome and how many attempts have already been made. “Third attempt, last outcome no answer” is a different call from “interested, asked to be called back today”.
• The company name, when the lead has one.
• A direct link into the lead in LumaKol, for when you want the full history.
• A reminder set for ten minutes before, which is enough time to read the history and finish what you are doing.

When a follow-up moves, the existing entry moves with it rather than a second one appearing beside it. A lead whose callback slips from Tuesday to Thursday shows up once, on Thursday. This is a small detail that decides whether a calendar stays usable after a month of real work or silently fills up with ghosts.

Personal and team feeds

There are two scopes. A personal feed shows the follow-ups on leads you own. A team feed shows the follow-ups across the people you are responsible for, which is what a team lead wants when planning the week or covering for someone on leave.

The feed never widens what you are allowed to see. It applies the same visibility rules as the app itself: an agent sees their own leads and only their own, so the team option is not even offered to them; a team lead sees the members of the teams they lead; a manager or owner sees the workspace. The link cannot be used to reach anything its owner could not already open in LumaKol, which means handing someone a feed URL by accident leaks their own view of their own work, not the company’s pipeline. Suspended workspaces stop serving the feed at all.

The honest limitation: this is a plan, not an alarm

Here is the part that usually goes unsaid in feature announcements, and it changes how you should use this.

A subscribed calendar is pulled, not pushed. Your calendar app decides when to come and re-read the file; LumaKol cannot make it do so. The feed asks to be refreshed every fifteen minutes, and Apple Calendar and Outlook broadly honour that request — a change you make in the app shows up in those calendars within minutes.

Google Calendar ignores the request and uses its own schedule. In practice that can mean several hours between refreshes, and Google publishes no guarantee about the interval. There is no setting you or we can change to speed it up. This is how Google treats every subscribed calendar from every provider, not something particular to LumaKol.

So use the feed for what it is genuinely good at: seeing your commitments in context. It answers “how full is Thursday afternoon?” and “can I take a site visit at three?” and “what has my team promised this week?” It should not be the thing that tells you a call is due in ten minutes.

That job belongs to the app. The push notification on the agent’s phone fires when the follow-up is actually due, from data that is never stale, and it opens straight onto the lead with the Call button in reach. The calendar is the plan for the day; the app is what says now.

If you reschedule a callback and want the customer’s promised time to be honoured to the minute, do not rely on a colleague’s Google Calendar having caught up. The due list in the app is the source of truth, and it always has been.

Using it well

1. Subscribe once on your laptop calendar, where you plan, rather than on every device. Most calendar accounts sync the subscription across your devices themselves.
2. Give the LumaKol layer its own colour. Being able to see at a glance which blocks are calls and which are meetings is most of the value.
3. Start the morning in the calendar to shape the day, and work the day from the app’s due list. The two are not competing; one is the map and the other is the clock.
4. Team leads: use the team feed for planning cover and spotting an overloaded week, not for supervision. A calendar is a poor management tool and a good planning one.
5. Rotate the link if you ever share your screen with it visible, or if you stop using the device you pasted it into.