A customer says, 'I can still see my request as open, but your team told me it was fixed.' Or a newly created record is missing. That does not always mean the customer portal is broken. The quickest way to help is to find out where the difference begins.
Here's a simple example
Northstar Foods reports that its cooler repair still shows 'In progress' in the portal. A member of your team believes the repair is finished.
HubSpot
What status does the team see?
Customer portal
What status can Maya see?
Comparison
Do both show the same permitted record?
First open the exact support request in HubSpot. If it still says 'In progress,' correct the underlying record if appropriate. If HubSpot says 'Closed' but the portal looks different, check the portal's configuration and displayed information.
Four things to check
1. Record
Is it correct in HubSpot?
2. Access
Can this customer see it?
3. View
Are filters hiding it?
4. Connection
Has the configured data setup been checked?
Record: Confirm the record ID, status and other values in HubSpot. Make sure you are not comparing two different requests with similar names.
Access: Sign in as the correct test customer. If the record belongs to another company or the customer's role does not allow access, it should not appear.
View: Check the portal's chosen object, list filters, stages and search settings. A request may exist but be excluded from a particular list.
Connection: Check whether the eligible HubSpot object has been selected and synchronized in the WoodsPortal administration setup. If the configured object mapping has changed, review and use the documented re-synchronization process as appropriate.
What if the customer sees the wrong record?
Stop and check permissions and record associations before making the list broader. A missing record is inconvenient; seeing another customer's information needs careful investigation. Use controlled test accounts and notify the person responsible for portal access.
HubSpot plan note. WoodsPortal's nested relationships between HubSpot objects use GraphQL. GraphQL is available with HubSpot Sales Hub Enterprise, Service Hub Enterprise, or Content Hub Professional or higher. Many other portal use cases can use WoodsPortal's REST API implementation on HubSpot plans including Free; supported features depend on the configuration.
What if the problem happens again?
Keep a short record of what happened: the customer account, record ID, value in HubSpot, value shown in the portal, any recent configuration changes, and the fix you tested. This helps your team tell a data problem from an access or screen-setting problem.
What happened
Request C-14 shows the old status
What we checked
HubSpot record, user role and portal view
What fixed it
Only record a verified change and result
Do not promise instant updates or automatic retries unless they have been verified for the specific WoodsPortal installation. Check the real behavior, record the outcome, and escalate persistent differences for technical review.
A short check before telling the customer it's fixed
Ask the test user to open the same request again. Confirm the correct status is visible, the customer still cannot see unrelated records, and an authorized update is reflected in HubSpot when relevant.
Frequently asked questions
Why is a record missing from my customer portal?
It may be outside the chosen list filter, not selected in the portal setup, not linked as expected or not permitted for that user. Check the HubSpot record and access rules first.
Does a HubSpot record change always appear instantly?
Do not assume a particular update time. Confirm the configured integration behavior and measure what happens in your own environment.
Should I give the customer broader permissions to make a record appear?
No. Verify the record relationship, view filter and intended user access first. Only change permissions when the business has approved the access.
Where should I check the correct status?
Start with the exact source record in HubSpot and the field the portal is configured to display.
Can a search filter hide an existing record?
Yes. Check the selected view, object, filters and stages. A record can exist in HubSpot but not belong in that particular list.
What should I record when reporting an issue?
Record the affected test account, record ID, expected and observed values, relevant settings and time. Avoid sending passwords or sensitive files.
How do I confirm the problem is fixed?
Repeat the original steps using the correct customer account and check both the portal view and underlying HubSpot record.
Make customer updates easier to trust
Start with the HubSpot record, then follow the information through the configured portal. Use the WoodsPortal object synchronization and record-filter guides if you need to inspect the setup.
Choose and synchronize HubSpot objects · Configure search and filters