Sometimes when something doesn’t behave as expected it can be a configuration issue or simply a feature that hasn’t been introduced into the platform yet. It doesn’t necessarily mean anything is broken, but it’s always worth reviewing together so we can confirm the best approach.
Teamgo has been developed largely from customer feedback since 2014, so we absolutely welcome enhancement requests. When something new is requested we review whether there’s already a solution available, whether it fits the broader platform roadmap, or whether it’s something we can scope as a custom improvement if needed.
In some cases features are added to the roadmap for wider release, and in others we can explore accelerated or customer-specific development depending on requirements and timing.
If you can share what outcome you’re trying to achieve, we’ll work with you to find the best path forward.
Teamgo Feature Requests & Enhancements
1. Is something “broken” if Teamgo doesn’t behave the way I expected?
Not necessarily. Sometimes a feature may behave differently than expected because:
the workflow is designed differently
there is another way to achieve the outcome
the configuration hasn’t been fully explored yet
or the functionality hasn’t been introduced into the platform yet
If something doesn’t seem right, we’re always happy to review it with you. Often there’s a solution available straight away — and if not, it may become a great opportunity for improvement.
2. Can Teamgo add new features if we need them?
Yes 👍 Teamgo launched in 2013 and has been shaped by customer feedback. Many of today’s core features — including contractor workflows, QR sign-in, emergency tools, badge printing, integrations, and automation — were introduced because customers asked for them.
We actively welcome enhancement requests and use them to guide platform development.
3. Why doesn’t Teamgo immediately build every requested feature?
Because we build responsibly and strategically. Our goal is to ensure improvements:
support real customer needs
align with the long-term platform direction
benefit multiple organisations where possible
maintain reliability and security across the system
Rather than building features just to match competitors or respond quickly to individual requests, we focus on delivering enhancements that create lasting value for customers.
4. What happens when I request a new feature?
When a request is submitted, we typically:
Review the requirement with you
Confirm whether an existing solution already exists
Assess whether configuration changes can solve the need
Evaluate suitability for the wider platform
Scope development effort if required
Determine whether it fits the roadmap or needs prioritisation
Every request is taken seriously and reviewed carefully.
5. Can features be built specifically for our organisation?
Yes — in some cases. If a feature is:
highly specialised
required urgently
organisation-specific
or outside the current roadmap
We can scope custom development. Depending on complexity and timing, this may involve:
a development contribution
expedited delivery pricing
or inclusion as part of a larger rollout initiative
We’ll always discuss options with you first.
6. Will other customers benefit from requested improvements?
Often, yes. Many enhancements requested by individual customers become part of the standard platform and are later used by organisations globally. This collaborative approach helps keep Teamgo practical, modern, and customer-driven.
7. Can feature requests be added to the roadmap instead of built immediately?
Absolutely! Some requests are best delivered as part of planned platform updates rather than custom development. When this happens:
the request is logged
prioritised alongside similar feedback
reviewed against platform direction
and scheduled appropriately
This ensures improvements are delivered in the most effective way for everyone.
8. What if we need something urgently?
Let us know. If timing is critical, we can:
explore configuration alternatives
recommend workflow adjustments
investigate integrations
scope accelerated development
or propose a staged solution
We’ll work with you to find the most practical path forward.
9. Are enhancement requests welcome even if they’re small ideas?
Yes — always. Suggestions may lead to:
workflow improvements
usability refinements
automation upgrades
reporting enhancements
integrations
or entirely new modules
Customer feedback is one of the most important drivers of Teamgo’s development.
10. How has customer feedback shaped Teamgo so far?
Since launching in 2014, Teamgo has grown almost entirely through customer-led innovation. Many features customers now rely on began as individual requests — including:
contractor workflows
QR code check-ins
visitor badge printing
emergency roll-call tools
workplace attendance tracking
integrations with identity platforms
compliance workflows
mobile access tools
and hybrid workplace features
Your feedback genuinely helps shape what comes next.
11. What’s the best way to submit a feature request?
Simply tell us what you’re trying to achieve. The most helpful requests include:
what outcome you need
who it affects
how often it would be used
whether timing is important
From there, we’ll explore the best solution together.
12. What’s Teamgo’s approach to platform improvements overall?
Our philosophy is simple: We don’t build features just to match competitors — we build features customers actually need.
Every enhancement is considered carefully to ensure it:
improves usability
strengthens security and reliability
supports real workplace workflows
benefits the broader customer community where possible
This approach is why Teamgo continues to evolve in practical, meaningful ways for organisations around the world.
Contact our team if you would like to discuss a new feature !