← All guides

Customer support · Taskending editorial team

Collect requests through a customer portal

A customer portal lets external users follow requests separately from internal team work. Correct roles and project access are the foundation.

· 1 min read

How to apply it

Invite the customer to Taskending with the appropriate customer role. Check the target project and access scope. Try a small request with a title, description and customer-facing response before wider adoption.

A concrete example

A customer reports a billing-report error. The team investigates internally, keeps technical discussion in internal notes and shares the solution through a customer-facing reply. The customer does not need to navigate internal projects.

What to watch for

Do not convert a real employee account merely to test customer behavior. Other customers’ requests and internal notes must stay outside the customer’s scope. Imported historical records may still need identity matching.

How to check the outcome

Verify that the customer sees their own request and response but cannot see another customer’s record or internal discussion.

Try it in your own workflow.

Create a company workspace and your first issue. Taskending is currently free.

Start for free

Keep reading

01
Customer support

Manage tickets from email, a portal and your API

Bring customer requests into one help desk workflow. Practical guidance on email deduplication, internal notes, customer visibility and linked development work.

02
Customer support

How to write a useful support request

Missing context creates extra correspondence before investigation can begin. Explain the problem, expected behavior and reproduction conditions clearly.

03
Customer support

Internal notes versus customer-facing replies

A request can contain both team discussion and customer correspondence. Visibility determines who may read each message.