It depends. I think it could be used more than once. Suppose the following US:

`As a user, I want to add some contacts manually to the suggestion list for possible duplicates. Selecting them from the contact list directly.`

In this case you will need to "force matchs" for all the user-selected contacts.

But, furthermore, I think adding a method like this is good because the programmer realizes about a distinction: those candidates coming from a matching algorithm and those coming from external sources. Compare the code for `adaptAndMerge()` now. It is obvious we are crafting a different kind of matching contact. You can follow the method ending in `Matcher.newForcedMatching()` which leads you to the inner function `newForcedMatching`. Its documentation says:

```javascript
// A forced matching is that not generated by the match algorithm.
// Consecuently, it does not include the `matchings` field.
```
Finally, as now is part of a public method and it has a definition, we can test if the exceptional object is right avoiding the root cause of this problem.

Have I convince you? ,)