|
|
| (26 intermediate revisions by 5 users not shown) |
| Line 1: |
Line 1: |
| Short summary of the incident. Usually 2-3 sentences that summarize the contents or the article.
| | {{Ph-I-Int}} |
| | |
| ==Background== | | ==Background== |
| Information about the product/service history to provide the necessary context surrounding the incident
| | {{Ph-I-B}} |
|
| |
|
| ==[Incident]== | | ==[Incident]== |
| Change title to be descriptive of the incident. Impartial and complete description of the events, including actions taken by the company, and the timeline of the incident coming to the public's attention.
| | {{Ph-I-I}} |
| === [Company]'s response === | | |
| If applicable add the proposed solution to the issues by the company.
| | ===[Company]'s response=== |
| | {{Ph-I-ComR}} |
| | |
|
| |
|
| ==Lawsuit== | | ==Lawsuit== |
| If applicable add any information regarding litigation around the incident here.
| | {{Ph-I-L}} |
| ===Claims===
| | |
| Main claims of the suit.
| |
| ===Rebuttal===
| |
| The response of the company or counterclaims.
| |
| ===Outcome===
| |
| The outcome, if any, of the suit.
| |
|
| |
|
| ==Consumer response== | | ==Consumer response== |
| Summary and key issues of prevailing sentiment from the consumers and commentators that can be documented via articles, emails to support, reviews and forum posts.
| | {{Ph-I-ConR}} |
| | |
|
| |
|
| ==References== | | ==References== |
| {{reflist}} | | {{reflist}} |
|
| |
|
| <includeonly>[[Category:Name of associated product, service, website, software, product line or company goes here]]</includeonly>
| | {{Ph-I-C}} |
| <noinclude>
| |
| [[Category:Article sample templates]]</noinclude>
| |