Account and access
Sign-in, workspace membership and access issues.
Sign in for product supportSupport
Find an answer or reach the right team.
Use public guidance for common questions, sign in for workspace-specific help, or route a security, billing or access issue to the correct owner.
Help desk
Choose the route that matches the issue.
Each destination is explicit. There is no decorative search field or hidden redirect.
Using Linkence
Workspace-specific product guidance and common tasks.
Sign in for product helpConnectors
Verified sources, permissions and available integrations.
Browse integrationsSecurity and vendor review
Controls, testing, deployment and document requests.
Open Security and TrustSupport coverage
Support from implementation through production.
The route and service depend on where you are in the engagement. Product support terms remain explicit in the selected plan or Order Form.
Implementation support
During a scoped production engagement, we work with your team on integrations, deployment, testing and rollout. Responsibilities and collaboration channels are agreed before implementation begins.
Product and workspace support
Get help with account access, workspace behavior, connected sources, knowledge processing and product issues. Workspace-specific investigation starts after sign-in or identity verification.
Ongoing improvement
Production fixes, monitoring, accuracy and performance improvements, and new agent or coworker responsibilities can continue after launch. The exact service follows the selected plan or Order Form.
Faster diagnosis
Send enough context to reproduce the issue.
A precise report protects your time and helps the right owner start with evidence instead of a clarification loop.
Include this context
- Organization and affected workspace
- Affected user, connector, document, agent or coworker
- Approximate time and steps to reproduce
- Exact visible error and a useful screenshot
- Expected result and what happened instead
Never include passwords, API keys, OAuth tokens or raw credentials.
What happens next
- RouteWe identify the product, access, connector, billing or security owner.
- InvestigateWe inspect the supplied evidence and reproduce the issue when possible.
- RespondWe provide the next action, a request for missing context or a scoped resolution path.
Support FAQ
Practical answers before you contact us.
These answers cover public support routing. Workspace and contract-specific terms remain available after sign-in or through your Order Form.
Which support channels and response targets apply?+
Support channels, operating hours and response targets follow your selected plan or Order Form. Linkence does not advertise one universal 24/7 phone, chat or email entitlement for every workspace.
How does support work during deployment?+
A scoped production engagement can include integration work, deployment planning, testing and rollout alongside your team. Owners, communication channels, environments and acceptance criteria are agreed before implementation.
What should I send for a connector or knowledge issue?+
Include the organization, affected connector or document, selected scope, approximate time, steps to reproduce and the exact visible error. Add a screenshot when useful, but never send passwords, API keys, OAuth tokens or raw credentials.
Can Linkence help with security or vendor review?+
Yes. Use the Security and Trust route for published controls and testing information, then use Contact for deployment boundaries or document requests that need review by the appropriate owner.
Where can I find workspace-specific product guidance?+
Sign in to open product documentation and help tied to the workspace experience. Public integration and security pages remain available without a workspace session.
Contact the right team
Still need help?
Sign in for workspace-specific support, or use Contact to route a security or access request.