Contact Support

Include These Details

1. Your screen size, browser, and whether the issue happened on desktop or mobile.

2. The active module, workspace, and record involved, such as company, deal, building, floor, or suite.

3. If it is a dashboard issue, note whether it happened in the start-here flow, the priority snapshot, the current-focus panel, or the advanced workspace.

4. Any AI prompt, export action, reminder trigger, or workflow step that led to the issue.

5. For upload issues, note the file type, whether extraction completed, whether the guided extractor auto-opened the comparison summary, and whether the document was saved without being marked parsed.

5a. If the problem is reopening a file after refresh, include whether you are on the same browser and device that uploaded it and whether the file opened immediately after upload but failed later.

5b. For Word proposal or counter uploads, include the exact heading labels used for economics sections, especially if the document uses layouts like Primary Lease Term, Rent Abatement Period, or Base Annual Net Rental Rate.

5c. If the file is a landlord response or tenant counter that still includes the original RFP pages above the response terms, mention that too so support can verify the response-layer parsing path.

6. For Austin inventory or map issues, include the building name or address and whether the issue was in the map, stacking plan, inventory list, or detail panel.

7. For Buildings tab issues, include the filters in use, the selected building, whether you were trying to add it to Surveys or another module, and whether the right-side result list stayed in sync with the map.

7a. If a deleted building or document came back after refresh, include the client workspace, the exact building name or document filename, whether you were signed in, and whether it reappeared immediately or only after sync.

8. If the issue involved suite selection, include the building, floor filter, suite status filter, selected suites, and whether the suites were added to Surveys correctly.

9. If the issue involved map drag-selection, include whether selection mode was on, how many buildings were expected, and whether the selection-only view matched the map box.

10. For shared CoStar import issues, include the workbook filename, whether the upload completed, and which building rows did or did not appear afterward.

11. For CRM intake issues, mention the building text you typed, whether an autofill suggestion appeared, whether you opened intake from the simple CRM landing or the advanced workspace, and whether you were trying to add a new building.

12. For stacking-plan or Financial Analyses handoff issues, include the building, floor, suite, whether the row came from a current lease or sublease upload or a manual edit, and whether the selected suites opened correctly in Financial Analyses.

13. For extraction or financial-analysis mismatches, include the metric that looked wrong, whether the document referenced the existing lease structure, and the page or clause where that carry-forward term appeared.

13a. If a document uploaded in Financial Analyses did not jump into the comparison summary automatically, include whether the file came through the guided extract panel, the tab-wide drag-and-drop overlay, the module document center, or an existing client-document selection, and whether the workspace showed an extraction error, stale saved data, or any scenario cards at all.

13b. If the Financial Analyses page still felt cluttered or something appeared in the wrong place, mention whether the issue was in the top intake area, the option cards, the active editor, or the exports and analytics section.

14. For shortlist or tour workflow issues, include the deal, building, floor, suite, the action you took in Buildings or CRM, and whether the shortlist entry or tour status updated where you expected.

15. If the issue was in the new CRM shortlist or tour boards, include the column you expected the item to appear in and whether moving it changed the linked deal stage correctly.

16. If the issue involved the new board filters, include the building filter, broker filter, date filter, and which cards should have remained visible.

17. If the issue was in a deal room tab, include the deal name, which tab you were in, and whether the problem was in Overview, Company, Updates, Listings, Tours, Negotiation, User Management, or Client View.

18. For deal-room summary issues, include the projected close date, current-location fields, move reason, or deal source you expected to see saved.

19. For negotiation tracker issues, include the negotiation line label, status, target value, latest value, and whether the update disappeared after refresh.

20. For deal-room access or client-view issues, include which internal or client member was affected, whether Client Access was on, and whether the curated client summary looked right.

21. If the issue involved AI tour briefs or AI proposal-request actions, include the exact card you used, the prompt or button clicked, and the response you expected to see.

22. If a follow-up task created from a tour card looked wrong, include the task title, expected due date, and the tour record it should have come from.

23. If drag-and-drop on the shortlist or tour boards did not work, include which card you dragged, the origin column, the target column, and whether the status changed after drop.

24. If a saved board view loaded the wrong slice, include the deal, saved view name, expected building or broker filter, and the date window you expected.

25. If a post-tour recap draft looked off, include the completed tour card, attendees, notes, and the specific subject or body text you expected the AI draft to reflect.

26. If shortlist owner or tour assignee updates did not stick, include the card, the expected owner or assignee, and whether the change disappeared after refresh or deal switch.

27. If a team-wide saved board view showed the wrong cards, include whether it was saved as deal-only or team-wide, the active deal, and the exact building, people, and date filters expected.

28. If Send to Client or Log to Deal Activity on a recap draft misbehaved, include the deal, tour card, client email on file, and whether the issue happened before or after the AI draft was generated.

29. If team-wide view permissions looked wrong, include your signed-in email, expected role, expected team, and whether the view should have been editable or read-only.

30. If bulk reassignment changed the wrong cards, include how many shortlist or tour cards were selected, the owner or assignee applied, and whether the visible filter slice matched the selected set.

31. If backend recap sending failed, include the client email on file, whether you were signed in, and whether the AI draft generated correctly before the send action was attempted.