|
|
(25 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 this section's title to be descriptive of the incident.
| | {{Ph-I-I}} |
|
| |
|
| 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.
| | ===[Company]'s response=== |
| | {{Ph-I-ComR}} |
|
| |
|
| ===[Company]'s response===
| |
| If applicable, add the proposed solution to the issues by the company.
| |
|
| |
|
| ==Lawsuit== | | ==Lawsuit== |
| If applicable, add any information regarding litigation around the incident here.
| | {{Ph-I-L}} |
|
| |
|
| ===Claims===
| |
| Main claims of the suit.
| |
|
| |
|
| ===Rebuttal=== | | ==Consumer response== |
| The response of the company or counterclaims.
| | {{Ph-I-ConR}} |
|
| |
|
| ===Outcome===
| |
| The outcome of the suit, if any.
| |
|
| |
| ==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.
| |
|
| |
|
| ==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>
| |