A housing SOC integrates GoPhish with existing staff phishing-report workflows. Which integration goal is most important?
Select an answer to reveal the explanation.
Short Explanation
Wire the GoPhish ‘I report this’ button into the same mailbox the housing SOC already watches. Clicks matter, but reporting is the behavior you actually want to grow. Do not orphan reports in a dark folder or a public chat.
Full Explanation
When a housing SOC integrates GoPhish with existing staff phishing-report workflows, the most important integration goal is to connect GoPhish report mechanisms to the existing phishing-report mailbox so SOC playbooks still receive staff reports. Reporting is the positive behavior awareness programs seek to grow; if reports die in an unmonitored folder or never reach playbooks, the municipality trains clicking metrics while starving the response path. Disabling report buttons so dashboards only count clicks and ignore positive reporting behavior optimizes for the wrong outcome and demotivates safe handling. Forwarding all reports to a public Slack channel including message bodies with any pasted secrets creates confidentiality and oversharing risk. Replacing the SOC mailbox entirely with an unmonitored GoPhish folder that staff cannot access orphans reports from operators who run the real playbooks. Exam caveat: GOAA GoPhish integration questions prioritize wiring simulations into living SOC report workflows. Operational check: map GoPhish report actions to the housing phishing-report mailbox, verify playbook tickets open on report, and keep click metrics secondary to report-and-respond health.